We use webhooks to let your application know when events happen, such as receiving an SMS message. When the event occurs, the system makes an HTTP request (usually a POST) to the URL you configured for the webhook. The request will include details of the event such as the incoming phone number or the body of an incoming message.
Send the request body with a Content-Type of application/json. Parameters such as charset=utf-8 are accepted.
Repeating a create with the same url and filter returns the existing webhook with 200 OK instead of creating a duplicate, even when name or rate_limit differ. The url must match exactly (no trailing-slash or letter-case normalisation). Filters match regardless of key order or value order, and sender, status, message_ref and campaign_id values also match regardless of letter case; event_type values must still be the upper-case names listed below. To change an existing webhook, use PUT /v2/webhook/{id}.
An account can have at most 25 webhooks. When the account already has 25, creating a new one returns 409 Conflict; delete a webhook with DELETE /v2/webhook/{id} before creating another. Repeating a create that matches an existing webhook still returns 200 OK at the limit, because no new webhook is created.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||