/infogreffe/companies/officers

POST /api/infogreffe/companies/officers

Price: 10 credits

Get the officers and management organs of a French company from the Infogreffe registry by SIREN (or SIRET): each officer's role, name, person type (individual or company), whether they can legally bind the company, term start/end dates, and — for individuals — first/last name, other given names, civility, gender, birth year and month, and nationality, or — for corporate officers — the officer company's SIREN, legal form, share capital and registered address.

How to use it

Get the officers (dirigeants / management organs) of one French company from the Infogreffe registry by SIREN (9 digits) or SIRET. Returns a list of officers, each with id, person_type (PP individual / PM company), name, role (e.g. Président, Directeur général, Administrateur), role_code, can_bind_company, is_active, start_date, end_date. Individuals also have first_name, last_name, other_names, title, gender, birth_year, birth_month, nationality. Corporate officers also have siren (use with infogreffe/companies), legal_form, capital and address.

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", "542051180"; minLength: 1)
• count integer required — Max number of officers to return (min: 1)

Response

• @type string (default: "InfogreffeOfficer")
• id string required
• person_type string nullable
• name string nullable
• role string nullable
• role_code string nullable
• can_bind_company boolean nullable
• is_active boolean nullable
• start_date string nullable
• end_date string nullable
• first_name string nullable
• last_name string nullable
• other_names array nullable
• gender string nullable
• birth_year integer nullable
• birth_month integer nullable
• nationality string nullable
• siren string 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
• 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

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.