/infogreffe/companies

POST /api/infogreffe/companies

Price: 20 credits

Get full French company details from the Infogreffe registry by SIREN (or SIRET): legal name, legal status, person type, registration and creation dates, declared activity and NAF activity (code/label), registered address, workforce range, employee count, legal form, share capital (amount/currency), fiscal year-end, social-economy / mission-company / single-shareholder flags and the beneficial owner declaration type.

How to use it

Get one French company from the Infogreffe registry by SIREN (9 digits) or SIRET. Returns one item with id, siren, name, legal_status (ACTIVE/...), person_type (PM corporate / PP natural), registration_date, creation_date, radiation_date, is_inactive, declared_activity, activity (NAF code/label), address (line_1..3, postal_code, city, country), workforce_range, employee_count, legal_form (code/label), capital (amount/currency/type), fiscal_year_end (DD-MM), is_ess, is_societe_mission, is_single_shareholder, at_legal_rep_domicile and beneficial_owner_declaration_type.

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: "652014051", "907739395"; minLength: 1)

Response

• @type string (default: "InfogreffeCompany")
• id string required
• siren string required
• name string nullable
• legal_status string nullable
• person_type string nullable
• registration_date string nullable
• creation_date string nullable
• radiation_date string nullable
• is_inactive boolean nullable
• declared_activity string nullable
• activity object nullable
  • @type string (default: "InfogreffeNafActivity")
  • code string nullable
  • label string nullable
• address object nullable
  • @type string (default: "InfogreffeAddress")
  • line_1 string nullable
  • line_2 string nullable
  • line_3 string nullable
  • postal_code string nullable
  • city string nullable
  • country string nullable
• workforce_range string nullable
• employee_count integer nullable
• legal_form object nullable
  • @type string (default: "InfogreffeLegalForm")
  • code string nullable
  • label string nullable
• capital object nullable
  • @type string (default: "InfogreffeCapital")
  • amount number nullable
  • currency string nullable
  • type string nullable
• fiscal_year_end string nullable
• is_ess boolean nullable
• is_societe_mission boolean nullable
• is_single_shareholder boolean nullable
• at_legal_rep_domicile boolean nullable
• beneficial_owner_declaration_type 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.