Skip to main content

Replay Webhook Delivery

The Replay Webhook Delivery endpoint manually retries a specific past delivery, identified by its deliveryId. It creates a brand-new delivery row for the attempt (the original row is left as-is) and immediately re-sends the event to the URL the original delivery was made to (not every URL configured on the webhook, if it has more than one).

When to use it​

Use this endpoint to retry a delivery that permanently failed (exhausted its automatic retries) after you have fixed whatever was wrong with your receiving endpoint, instead of waiting for the same event to occur again.

Example request​

curl -X POST "https://api.turbodocx.com/api/webhooks/signature/replay" \
  -H "Authorization: Bearer $TURBODOCX_API_KEY" \
  -H "x-rapiddocx-org-id: $TURBODOCX_ORG_ID" \
  -H "Content-Type: application/json" \
  -d '{"deliveryId": "d3a1c2b4-5e6f-4a7b-8c9d-0e1f2a3b4c5d"}'

Get deliveryId from List Webhook Deliveries.

Example response​

On success the endpoint returns 200 OK with the new delivery:

{
  "data": {
    "id": "f2e1d0c9-8b7a-4695-a3b2-1c0d9e8f7a6b",
    "eventType": "signature.document.completed",
    "url": "https://example.com/webhooks/turbodocx",
    "attemptCount": 0,
    "maxAttempts": 3,
    "isDelivered": false,
    "status": "pending",
    "createdOn": "2026-05-02T09:30:00.000Z",
    "updatedOn": "2026-05-02T09:30:00.000Z"
  },
  "message": "Webhook delivery replayed successfully - new delivery attempt created"
}

Check the new delivery's status afterward with List Webhook Deliveries.

Common errors​

StatusWhenResponse body
401Missing or invalid API key/token, or the organization cannot be resolvedEmpty (status only)
403The key's role is not administratorEmpty (status only)
404No webhook with that name exists, or deliveryId does not belong to it{ "error": "Webhook or delivery not found" }
400deliveryId is missing or not a valid UUIDValidation error from the body schema
Last updated on