message.status webhook event — not as an inbound message. It never enters the inbox and never creates a conversation, so it can’t flood your threads. You only receive it if you explicitly subscribe.
message.status is currently emitted for the WhatsApp Alternative channel only. It is opt-in: add message.status to your sender’s webhookEvents. Media bytes are not downloaded — only metadata and any text/caption is delivered.Subscribe
Addmessage.status to the sender’s subscribed events (via the API or the dashboard):
The message.status event
message.status
Fields on data
| Field | Present | Description |
|---|---|---|
from | always | The contact who posted the status, in E.164. |
to | always | Your linked number. |
channel | always | whatsapp_alt. |
messageType | always | The story type: text, image, video, or audio. |
text | when present | The caption, or the text of a text story. |
mimetype | media stories | MIME type of the story media (bytes are not included). |
providerTimestamp | when known | When WhatsApp originally received the status (Unix ms). |
Handling it
Your own status posts are not delivered — only statuses from your contacts trigger the event. Media bytes are intentionally omitted; use
messageType and mimetype to know the story kind.Next steps
Groups
Identify group messages and their author.
Receiving Messages
Configure and verify your sender webhook.
