Webhook Events

WhatsApp Business Account restricted or reinstated

Meta restricted, disabled, deleted or reinstated a connected WhatsApp Business Account, or flagged a violation on it.

When it fires

Mirrors Meta's account_update events. They apply to the whole WhatsApp Business Account, so every connected number on it receives one event.

Payload notes

Branch on status.status (restricted or active) and status.metaEvent. status.restrictions lists what Meta restricted (for example RESTRICTED_BIZ_INITIATED_MESSAGING) and when each lifts. The same status is on the account as platformStatus.

postWebhookwhatsapp.account.status_updated

Payload

idstring required

Stable webhook event ID: the dedupe key, also sent as the X-Zernio-Event-Id header and identical on every retry and redelivery. It identifies the event only, never an account or other resource.

testboolean

Always true when present: only a sample sent by POST /v1/webhooks/test with an event carries it. Real deliveries never do.

event'whatsapp.account.status_updated' required
timestampstring date-time required

UTC time at which Zernio generated this event (set once when the event payload is built, before delivery is queued). Retries and redeliveries keep the original value, so it reflects the event, not the delivery attempt.

Example payload

{
  "profiles": [
    {
      "externalId": "tenant_42"
    }
  ]
}

Response

Webhook received successfully

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.