Message status | Chat Bridge

Chat Bridge notifies each status change of a sent message through an HTTP POST request (webhook).

The normal flow is SENT → DELIVERED. FAILED is terminal: no more events are received for that message_id after it. Not every message reaches DELIVERED: it depends on whether the mask/operator reports the delivery receipt, so some messages remain in SENT as their final successful state. Your endpoint must accept application/json and respond with a 2xx HTTP code; the response body is ignored.

Chat Bridge notifies each status change of a sent message through an HTTP POST request (webhook). The normal flow is `SENT` → `DELIVERED`. `FAILED` is terminal: no more events are received for that `message_id` after it. Not every message reaches `DELIVERED`: it depends on whether the mask/operator reports the delivery receipt, so some messages remain in `SENT` as their final successful state. Your endpoint must accept `application/json` and respond with a 2xx HTTP code; the response body is ignored.

Payload

The payload of this webhook request is an object.

message_idstringOptional

The same message_id returned in the 202 response of the send.

statusenumOptional

Status of the message. SENT when it was accepted and sent by the SMS provider; DELIVERED when the provider confirmed delivery to the recipient’s device; FAILED when the send or the delivery failed (terminal: no more events are received after it).

datetimedatetimeOptional

Timestamp of the status change, in UTC.

origin_identifierstringOptional

Only present when this SMS is the automatic fallback of a WhatsApp or RCS send (see the fallback field of those APIs): message_id of the originating send, to correlate both attempts. If the backup SMS also fails, a final event with status: FALLBACK_EXHAUSTED is emitted (documented in the WhatsApp and RCS APIs). Absent on regular sends.

Response

200

Event received and processed by the client.