WhatsApp suppression webhooks
whatsapp_suppression.created fires when a suppression opens on the workspace's suppression list, so your own systems can see new blocks without polling.
The payload
Code example
{
"type": "whatsapp_suppression.created",
"timestamp": "2026-08-25T14:52:03.192524705Z",
"data": {
"suppression_id": "was_01krdgeqcxet5s7t44vh8rt9mg",
"address": "+14155550100",
"waba": null,
"reason": "manual",
"workspace_id": "ws_01ky7m21hjffh9s8kq76gyb1xf"
}
}suppression_idnames the suppression.addressis the suppressed number in E.164 format.wabais the WhatsApp Business Account the block is limited to, ornullwhen it covers the whole workspace, whichever account sends.reasonsays why the suppression opened.workspace_idis the workspace that owns the list.
What does not fire
Only openings fire an event. Ending a suppression does not yet, so re-read the list before treating a mirrored block as still standing.
An opt-out the recipient stated themselves is a preference rather than a suppression, and fires preference.revoked instead.
Next steps
- Suppressions: how a suppression blocks sends and how to manage the list
- Preferences: opt-outs the recipient stated themselves
Related resources
Continue with the documentation, guides and examples for this topic.