Webhook Delivery Failures
Successful Delivery
Dialpad considers a Webhook notification successfully delivered when your endpoint returns any HTTP 2xx response. The default HTTP request timeout is 5 seconds, so your endpoint should respond promptly.
Retry Behavior
500 Errors
Dialpad schedules retries when your endpoint returns a 5xx response.
| Event type | Maximum retries after the initial attempt | Approximate Backoff Sequence |
|---|---|---|
| Call and PowerDialer | 3 | 2, 4, and 8 seconds |
| SMS | 10 | 30 seconds; then 1, 2, 4, 8, 16, and 32 minutes; then three 60-minute waits |
| Contact, phone, fax, status, and change events | 4 | 0.1, 0.2, 0.4, and 0.8 seconds |
These intervals are approximate. Request duration and queue delays can increase the elapsed time.
400 Errors
4xx responses, including 429 Too Many Requests, do not trigger scheduled retries.
Timeouts or Connection Failures
Connection failures may receive up to two additional retries in quick succession. Backoff Sequences are not supported.
Frequently Asked Questions
| Does a Failing Webhook get Deleted or Disabled after a certain amount of time? |
|---|
| No, event subscriptions must be manually disabled or deleted by the developer. |
| Can Retires be received after other events for the same call or conversation? |
|---|
| Yes, depending on the backoff schedule for the event you can receive events out of order. |
Updated about 7 hours ago
Did this page help you?