Overview
Manually triggers a retry for a webhook delivery that is inFAILED status. This resets the delivery to PENDING and schedules an immediate dispatch attempt.
Endpoint
Authentication
Requires a valid API Key with thepartner_webhooks_manage permission.
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
id | UUID | Yes | The delivery ID (from GET /partners/webhooks/deliveries). |
Example Request
Success Response
HTTP Status:200 OK
Error Responses
| HTTP Status | Code | Description |
|---|---|---|
401 | UNAUTHORIZED | Missing or invalid API key |
403 | FORBIDDEN | Missing partner_webhooks_manage permission |
404 | RESOURCE_NOT_FOUND | Delivery not found, or delivery belongs to a different partner |
404 | DELIVERY_NOT_RETRYABLE | Delivery is not in FAILED status (cannot retry PENDING or DELIVERED deliveries) |
Notes
- Only
FAILEDdeliveries can be manually retried. - After calling this endpoint, the delivery status changes to
PENDING. The system will attempt dispatch immediately. - The
errorfield is cleared when a retry is initiated. If the retry fails, it will be set again. - There is no limit on the number of manual retries.
- The delivery’s
attemptCountcontinues to increment with each retry.
Related Endpoints
GET /partners/webhooks/deliveries— List deliveries and findFAILEDones