> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.chatbridge.mx/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.chatbridge.mx/_mcp/server.

# Call result

POST 

Chat Bridge notifies the final status of each launched call through an HTTP POST request (webhook).

To enable notifications you must provide the Voices team with the destination URL, which is configured in your App-Key. Optionally, you can define HTTP headers with constant values (for example, an authorization token) that will be sent with each webhook.

If the call performs a transfer, separate events are emitted for the initial call and for the transfer (`call_type = transfer`). Your endpoint must accept `application/json` and respond with a 2xx HTTP code.

Reference: https://docs.chatbridge.mx/blaster/webhooks/call-result-webhook

## Request

### Payload

- `message_id` (string, optional) — Unique identifier of the call generated when it is created.
- `status` (enum, optional) — Overall status of the call. `SENT` when it finishes successfully (sip_code = 200); `TO_REDIAL` when the attempt failed with a redialable SIP code and the call will be retried automatically (only when `retry` was configured and attempts remain); `FAILED` for the final failure.
  - Allowed values: `SENT`, `TO_REDIAL`, `FAILED`
- `operator` (string, optional)
- `is_mobile` (boolean, optional)
- `outbound_route` (string, optional)
- `phone_number` (string, optional)
- `sip_code` (integer, optional) — SIP code returned by the phone platform when finishing.
- `sip_description` (string, optional) — Human-readable description corresponding to the SIP code.
- `call_type` (enum, optional) — Call type. `initial` for the main call; `transfer` when it corresponds to a transfer.
  - Allowed values: `initial`, `transfer`
- `duration_minutes` (integer, optional)
- `duration_seconds` (integer, optional)