Developers

Connect your tool to Cortex preparation.

Understand the Cortex API path, key authentication, the rights required and treatment tracking before export.

GET /api/v1/user/credits HTTP/1.1
Host: cortex-compta.ch
Authorization: Bearer YOUR_API_KEY

Authenticate every request

The API uses a key in the Authorization: Bearer header. Keys are managed after sign-in. Keep them on the server and grant only the rights needed.

A 401 means missing or invalid authentication. A 403 means the key or the file lacks the required rights. A rate limit may return 429.

Deposit, follow, then collect

The deposit starts a treatment. Fetch its state before using the prepared information. A finished treatment is not an accounting validation.

Export generation is also tracked by its identifier. Download the file only when it is available. File rights and controls still apply.

POST /api/v1/documents/upload — deposit a document.
GET /api/v1/documents/:id — read a document.
GET /api/v1/treatments/:id — follow a treatment.
POST /api/v1/exports/generate — request an export.
GET /api/v1/exports/:id — follow its preparation.
GET /api/v1/exports/:id/download — collect the available file.

Formats actually exposed

GET /api/v1/formats currently lists cresus, winbiz, sage, abacus, banana, wineur and excel. DATEV and ZIP exist as file exports after human validation, outside this API list.

cresus
winbiz
sage
abacus
banana
wineur
excel

See the nine file formats

Test with a file you control

Start with test documents that hold no confidential data. Handle errors, processing delays and retries explicitly to avoid duplicate deposits.

Detailed documentation and the parameter schema are available after sign-in. Check the formats and rights of your plan before integrating the path.

Ask an integration question