/infogreffe/officers/appointments

POST /api/infogreffe/officers/appointments

Price: 10 credits

Get all corporate appointments (mandates) held by a French company director or officer across every company, from the Infogreffe registry, by their person id (obtained from infogreffe/officers/search). Returns one entry per company the person is linked to, each with the company id, country and the list of roles held there — role label and code, whether the role can legally bind the company, whether it is a shareholder role, whether it is active, and the term start and end dates.

How to use it

Get all corporate appointments of one French director/officer across every company from the Infogreffe registry. Pass person_id (the id field from infogreffe/officers/search) and count. Returns a list of appointments, each with company_id (the company UUID — use infogreffe/officers/search to resolve its name and SIREN), country, and roles — a list of mandates held at that company, each with role (e.g. Président, Directeur général, Gérant, Associé), role_code, can_bind_company, is_associate, is_active, start_date and end_date. Some company links carry no role detail and have an empty roles list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• person_id string required — Person UUID (id) of a director or officer, as returned by infogreffe/officers/search (examples: "fd887fd3-46b1-4c68-8e88-23b225638ce9"; minLength: 1)
• count integer required — Max number of appointments to return (min: 1)

Response

• @type string (default: "InfogreffeAppointment")
• company_id string required
• country string nullable
• roles array nullable
  • @type string (default: "InfogreffeAppointmentRole")
  • role string nullable
  • role_code string nullable
  • can_bind_company boolean nullable
  • is_associate boolean nullable
  • is_active boolean nullable
  • start_date string nullable
  • end_date 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 — Officer not found (no person matches the given person id) 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.