API and integrations

The API page connects the PBX to your tools: CRM, billing, dashboard.

API keys

A key lets a tool act on the PBX with the rights of the chosen role. Give it a purpose (“CRM”), a role and, if you want, an expiry date, then Create the key. Copy it right away: it will not be shown again. Revoke cuts off access for the tool that uses it.

The API documentation of your space is served at the portal’s /api/docs/en address (/api/docs in French; OpenAPI description: /api/v1/openapi-client.en.json and /api/v1/openapi-client.json). An error carries a stable code and a detail; with the Accept-Language: en header, the detail is in English. Each key can send 300 requests in a row, then 10 per second; beyond that, the response is 429 (trop_de_requetes) with Retry-After, the number of seconds to wait. A key also connects an AI assistant: see AI assistants (MCP).

Webhook

A webhook notifies your tool of each event, by calling an https address of your choice:

• new voicemail;
• call recorded.

Each delivery is signed with a secret (X-Centrex-Signature header): this way your tool checks that it really comes from the PBX. The secret is shown only once; New secret creates another one. Recent deliveries shows each delivery, its attempts, its status and the cause of the last failure (address refused, host not found, unreachable, error response with its code). After 20 consecutive failures, the webhook turns itself off: the date is shown; saving it again turns it back on.