List Webhooks
Parameters
Request
Response
Fields
Create Webhook
secret is provided, one is generated automatically.
The secret field is returned only in the creation response. Store it securely — it is used to verify delivery signatures and cannot be retrieved later.
Parameters
Request
Response
Get Webhook
Parameters
Request
Response
Fields
Same as List Webhooks fields.Update Webhook
PATCH for partial updates. The secret cannot be changed through this endpoint.
Parameters
Request
Response
Delete Webhook
Parameters
Request
Response
Returns204 No Content on success.
Test Webhook
ping event to the webhook’s target URL. The delivery is processed asynchronously — check the List Deliveries endpoint to see the result.
Parameters
Request
Response
List Deliveries
Parameters
Request
Response
Delivery Fields
Get Delivery
Parameters
Request
Response
Same format as individual items in List Deliveries.Event Types
Delivery Statuses
Retry Behavior
Failed deliveries are retried automatically with exponential backoff. Avala makes up to 5 retry attempts before marking a delivery asfailed.
Retry rules:
- 2xx responses are treated as successful. No retry.
- 4xx responses (client errors) are not retried. These indicate a problem with your endpoint (bad URL, auth failure, rejected payload). Fix your endpoint and use the Test Webhook endpoint to re-verify.
- 5xx responses and network errors (timeout, connection refused) are retried with the backoff schedule above.
- The
next_retry_atfield on a delivery shows when the next attempt is scheduled. It isnullfor delivered or permanently failed deliveries.
Signature Verification
Every delivery includes anX-Avala-Webhook-Signature header. Verify it using the secret from when you created the webhook:
Error Responses
Validation Error (400)
Unauthorized (401)
X-Avala-Api-Key header is missing or contains an invalid key.