sent, delivered, read, or failed. Use it for delivery tracking, read confirmation, and audit trails.
It is configured per WhatsApp sender, so different senders can point at different endpoints.
Webhook Configuration
To enable read receipts for a sender:- Edit your WhatsApp sender and open the Read Receipts Webhook section
- Enter your Webhook URL and save
- A Signing Secret is generated automatically — use it to verify the signature on each request
whatsapp_message_id returned by the Send Template and Send Free-form endpoints, so you can match every update to the original message.
Request Format
The webhook is sent as a POST request to your configured URL with a JSON body and anX-Signature-256 header.
Payload Structure
string
The event type. Value:
message_statusinteger
Numeric identifier of the message — the same
whatsapp_message_id returned when you sent the message. Use this to correlate the status update with the original send.string
Provider message identifier for messages sent over Twilio, or
nullstring
Provider message identifier (WhatsApp
wamid) for messages sent over the Meta Cloud API, or nullstring
Unique identifier (UUID) of the conversation the message belongs to, or
nullstring
Unique identifier (UUID) of the assistant connected to the sender, or
nullobject
The WhatsApp sender the message was sent from
string
The recipient phone number
string
The sender phone number
string
Message direction. Value:
outboundstring
The new delivery status. Possible values:
sent, delivered, read, failed, undeliveredinteger
Provider error code when
status is failed or undelivered, otherwise nullstring
Raw provider error message when the message failed, otherwise
nullstring
Human-readable description of the error, otherwise
nullstring
ISO 8601 timestamp of when the platform recorded the status change, in the WhatsApp number owner’s configured timezone
string
ISO 8601 timestamp of the carrier’s own event time, in the owner’s configured timezone. Present for messages sent over the Meta Cloud API;
null over Twilio (Twilio’s status callback does not include an event time). Prefer this when present — it is the carrier’s authoritative time.Verifying the Signature
Every request includes anX-Signature-256 header containing an HMAC-SHA256 of the raw request body, keyed with your sender’s Signing Secret:
Retry Behavior
If your endpoint returns a non-2xx status or the request fails, delivery is retried:
Server errors (5xx) and rate limits (429) are retried. Client errors (4xx) are treated as a misconfigured endpoint and are not retried.
Important Notes
- The webhook is configured per sender — each sender can have its own URL and secret.
- Events triggered by the Make test request button in the sender settings include an extra
test: truefield and use placeholder values. Real status updates never includetest. readonly fires if the recipient has read receipts enabled in their WhatsApp privacy settings.deliveredalways fires.- Statuses can arrive out of order or be re-sent by the provider. We only forward genuine forward progress, so you won’t receive a
deliveredafter areadfor the same message — but you should still treat the webhook as the source of truth and de-duplicate bywhatsapp_message_id+status. timestampis always the time the platform recorded the change (in the number owner’s timezone).provider_timestampis the carrier’s authoritative event time when available — prefer it for accuracy, and fall back totimestampwhen it isnull.- Use Regenerate in the sender settings to rotate the signing secret if it is ever exposed.

