Skip to main content
POST
Registers an HTTPS endpoint to receive signed events. An account may have up to 20 endpoints. The response includes the signing secret — returned here (and on rotation) — which you store to verify signatures.
These are the partner webhook control plane endpoints (HMAC-signed, retried, replayable). They are distinct from the per-list Delivery Forwarding webhooks configured in the dashboard.

Body Parameters

string
required
An https:// URL, max 2000 characters, resolving to a public host (private/loopback addresses are rejected).
array
required
A non-empty list of supported event types, including message and business-profile events. message.clicked and the staged webhook.delivery_dead event require explicit subscriptions.
Include message.clicked to receive tracked message-link clicks, including bots and repeat clicks. Existing endpoints do not gain click subscriptions automatically. See the click payload.

Examples

The additive failure fields and destination recovery controls are part of a staged release. active records your configured state; effectiveActive also accounts for operational disablement. See destination failure and recovery and delivery history.

Error Codes

Next Steps

Verify signatures

Validate the HMAC on every event.

List endpoints

See all endpoints on the account.