> 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.

# Batch status

POST 

Sent once per batch created with `webhook_mode: BATCH`, when every number has a send result (usually about 1 minute after the request). If a number is still pending after 30 minutes, the webhook is sent anyway with that number as `QUEUED_PROVIDER`.

After this webhook, only later changes of a number (a `DELIVERED`, a `READ` or a late `FAILED`) are notified individually with `batch_id`; a status already included here is not repeated. A batch that could not be processed is notified with `status: FAILED`, an `error` and the `unprocessed` list, in any `webhook_mode`.

Reference: https://docs.chatbridge.mx/rcs/webhooks/rcs-batch-status-webhook

## Request

### Payload

- `type` ("BATCH", optional) — Always `BATCH`. Distinguishes this webhook from the individual ones.
- `batch_id` (string, optional)
- `status` (enum, optional)
  - Allowed values: `COMPLETED`, `FAILED`
- `datetime` (datetime, optional)
- `total` (integer, optional)
- `summary` (map from string to integer, optional) — Number of recipients per status (`COMPLETED` only).
- `messages` (list of RcsBatchStatusEventMessagesItems, optional) — Status of each number, in the order of the request.
- `error` (string, optional) — Reason of the failure (`FAILED` only).
- `unprocessed` (list of string, optional) — `message_id` that were never sent (`FAILED` only).

## Types

### RcsBatchStatusEventMessagesItems

- `message_id` (string, optional)
- `status` (string, optional)
- `datetime` (datetime, optional)