Webhooks
Create, list, update, delete webhooks and manage webhook logs.
Create a webhook for the application
Creation starts unsigned endpoint verification; then configure an enabled channel binding and subscriptions to receive events. Normal delivery accepts any 2xx within 30 seconds; validation accepts any 2xx containing the token within 10 seconds.
List webhooks for the application
List webhooks for the application
Retrieve a webhook
Requires an application API key. Returns only a webhook owned by that application; unknown and cross-application IDs return the same 404 response.
Update a webhook
Update a webhook
Delete a webhook
Delete a webhook
Get webhook delivery performance
Returns average delivery latency, unresolved failure count, and current health for one webhook. The API key determines the application and webhooks owned by another application are reported as not found.
Regenerate the webhook signing secret
Regenerate the webhook signing secret
List webhook logs
List webhook logs
Retry a webhook log
Replay preserves the recorded body, timestamps, expiry and delivery ID, and uses the current endpoint/authentication and a fresh signature. Validation retry uses a new token and can verify/reactivate the webhook. Live delivery has no general automatic retry guarantee.
Retry multiple webhook logs
Only event logs are supported. Use canRetryBulk from the log listing to select eligible logs; validation logs can only be retried individually.
Get webhook event configuration for a channel
Returns the subscribed event types and enabled state for a webhook on a specific application channel. Returns an empty events list if no configuration exists. This is the standard API-key route for a pending or completed Sandbox application channel. The webhook and channel must belong to the exact application authenticated by the API key.
Configure webhook events for a channel
Sets which event types a webhook receives for a specific application channel. Sending an empty events array removes the configuration (unsubscribes the webhook from that channel). This is the standard API-key route for a pending or completed Sandbox application channel. The webhook and channel must belong to the exact application authenticated by the API key. For WhatsApp Coexistence contact/history import, subscribe one active channel webhook to `message` and `message_echoes` before starting in the dashboard. WhatsApp also supports exact subscriptions to partner_app_uninstalled and account_disconnected; these events are delivered before the matching channel is removed. Deduplicate retries with providerEventId or X-Hub-Delivery-Id.