Resend a delivery
Re-fire a finished-URL callback delivery now, with freshly enriched payload.
Details
| Description | Resets the delivery so the worker picks it up on its next drain tick (within a few seconds): status flips to pending, the attempts counter resets to 0, and next_attempt_at is set to now. The worker re-signs fields like recording_url fresh and writes the new body back into payload. |
|---|---|
| HTTP Method | POST |
| Endpoint URL | /v1/applications/:id/deliveries/:deliveryId/resend |
| Authorization | API key as a bearer token — Authorization: Bearer $VOYLO_API_KEY. Both the application and the delivery must belong to the key's workspace, otherwise 404. See Authentication. |
Request parameters
| Parameter | Description | Location | Constraints | Default |
|---|---|---|---|---|
id | The application's id. | Path | uuid (required) | — |
deliveryId | The delivery's id. | Path | uuid (required) | — |
Request example
cURL
curl -X POST \ https://voylo.ai/v1/applications/8f3b1c2e-9a4d-4e7f-8b21-6c5d4e3f2a1b/deliveries/d1e2f3a4-b5c6-7d8e-9f01-2a3b4c5d6e7f/resend \ -H "Authorization: Bearer $VOYLO_API_KEY"
Success response
204 No Content — the delivery is queued for re-send; the response body is empty.
Possible errors
| Error | Description |
|---|---|
| 400 Bad Request | id or deliveryId is not a valid UUID. |
| 401 Unauthorized | API key is missing, invalid, or revoked. |
| 403 Forbidden | The key's role doesn't permit this action. |
| 404 Not Found | No such application/delivery in the key's workspace. |
Re-send is asynchronous — a
204 means the delivery was queued, not that your endpoint accepted it. Poll the delivery for the new status / responseStatus.