WEBHOOKS
Retry policy
Understand automatic delivery retries, exponential backoff and terminal failure behavior.
Real-time
Event driven
As events happen
Reliable delivery
Automatic retries
Exponential backoff
Signatures
HMAC SHA-256
Verify every payload
Endpoint limit
100 endpoints
Per tenant
Payload
JSON
Versioned envelope
Successful delivery
Any valid 2xx response acknowledges the event and ends retry processing.
Retry schedule
| Attempt | Approximate delay |
|---|---|
| 1 | Immediate |
| 2 | 1 minute |
| 3 | 5 minutes |
| 4 | 30 minutes |
| 5 | 1 hour |
| Later attempts | Progressive exponential backoff |
Backoff strategy
Retries use exponential backoff with jitter to reduce synchronized retry spikes.
Maximum attempts
Failed deliveries are retried for a bounded period and attempt count; exact production policy is exposed in endpoint metadata.
Non-retryable responses
| Response | Behavior |
|---|---|
| 2xx | Success |
| 408 / 429 | Retry |
| 5xx | Retry |
| Most 4xx | Failure/configuration issue |
Endpoint disabling
Repeated terminal failures can surface endpoint health warnings and may require operator action.
Best practices
Acknowledge quickly, queue work asynchronously, and make processing idempotent.