/infogreffe/companies/insolvency

POST /api/infogreffe/companies/insolvency

Price: 10 credits

Get the collective insolvency proceedings (procédures collectives) of a French company from the Infogreffe registry by SIREN (or SIRET): whether the company has a recorded proceeding, the proceeding type (safeguard, judicial reorganisation, judicial liquidation), its opening date, the registering commercial court (greffe) and the procedure reference number. Companies with no proceeding return an empty list.

How to use it

Get the collective insolvency proceedings (procédures collectives) of one French company from the Infogreffe registry by SIREN (9 digits) or SIRET. Returns an empty list when the company has no recorded proceeding; otherwise one item with id, siren, has_detail, proceeding_type (e.g. 'Liquidation judiciaire', 'Redressement judiciaire', 'Sauvegarde'), proceeding_type_code, opened_at (YYYY-MM-DD), greffe (code/label) and procedure_number. When has_detail is false the proceeding is recorded but its judicial details are not publicly available (type/date/court/number are null).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• siren string required — French company SIREN (9-digit registration number) or SIRET (examples: "514010669", "410316491"; minLength: 1)

Response

• @type string (default: "InfogreffeInsolvency")
• id string required
• siren string nullable
• has_detail boolean nullable
• proceeding_type string nullable
• proceeding_type_code string nullable
• opened_at string nullable
• greffe object nullable
  • @type string (default: "InfogreffeGreffe")
  • code string nullable
  • label string nullable
• procedure_number string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Company not found (well-formed but nonexistent SIREN, or no matching company in the registry) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.