# /infogreffe/companies/financials

`POST /api/infogreffe/companies/financials`

Price: 10 credits

Get the yearly key financial figures filed by a French company in the Infogreffe registry by SIREN (or SIRET): one entry per filed annual account, each with the accounting closing date, fiscal period length in months, currency, revenue (chiffre d'affaires), net result (profit or loss), employee count and whether the figures are kept confidential. Returns an empty list for companies that have not filed any accounts.

## How to use it

Get the yearly key financials of one French company from the Infogreffe registry by SIREN (9 digits) or SIRET. Returns a list of filed annual accounts, each with id, closing_date (YYYY-MM-DD), fiscal_period_months, currency, revenue (chiffre d'affaires, can be 0 or null when not disclosed), result (net profit/loss, can be negative or 0), employee_count and is_confidential (true when revenue/result are withheld). A company may have several entries for the same closing year (different filings). Empty list means no accounts filed.

## 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)

## Response

### 200 — Successful Response

- `@type` (string) (default: "InfogreffeFinancial")
- `id` (string, required)
- `closing_date` (string, nullable)
- `fiscal_period_months` (integer, nullable)
- `currency` (string, nullable)
- `revenue` (integer, nullable)
- `result` (integer, nullable)
- `employee_count` (integer, nullable)
- `is_confidential` (boolean, nullable)

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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)

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.