/infogreffe/officers/search

POST /api/infogreffe/officers/search

Price: 20 credits

Search French company directors and officers in the Infogreffe registry by name. Returns matching persons, each with id, name, first/last name, birth year and a list of their mandates (role, role code, company id, company name and SIREN).

How to use it

Search French company directors/officers (dirigeants) in the Infogreffe registry by name. Pass a query (person name) and count. Returns a list of persons, each with id, name, first_name, last_name, birth_year and mandates — a list of their corporate appointments, each with role (e.g. ORGANE, ENTREPRENEUR_INDIVIDUEL, BENEFICIAIRE_EFFECTIF), role_code, company_id, company_name and siren. Use the siren with infogreffe/companies for full company details.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Search query — director or officer name (examples: "dupont", "bernard arnault"; minLength: 1)
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "InfogreffeOfficerSearchItem")
• id string nullable
• name string nullable
• first_name string nullable
• last_name string nullable
• birth_year integer nullable
• mandates array nullable
  • @type string (default: "InfogreffeOfficerMandate")
  • role string nullable
  • role_code string nullable
  • company_id string nullable
  • company_name string nullable
  • siren 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 — No officers matched the search query 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.