Replay a delivery

Send a past delivery's event to its endpoint again, as a new delivery with the same event ID.

POST{BASE_URL}/webhooks/deliveries/{id}/replay

Queues the delivery's event to be sent to the same endpoint again, as a new delivery. Use it after your endpoint was down and has been fixed. Requires a provider key; the partner header is ignored. Send no body.

  • The original delivery is left as it was.
  • The new delivery carries the same event ID and payload, so a receiver that already processed the event recognises it as a duplicate.
  • It goes through the queue, with the usual retries. The answer is 202: follow the new delivery with Retrieve a delivery.
  • It is marked isTest: true, because it is not a new occurrence.

Path parameters

idstringrequired
The ID of the delivery to replay.

Response

dataobjectrequired
The new delivery, with status PENDING.

Status codes#

StatusCodeMeaning
202—Queued.
403provider_key_requiredA partner key made the call.
404webhook_delivery_not_foundYou have no delivery with that ID.
409webhook_endpoint_disabledThe endpoint is disabled. Enable it first.
409webhook_replay_connection_inactiveThe delivery is about a partner whose connection is no longer active — it paused or disconnected you.
curl -X POST "$LOCALOY_BASE_URL/webhooks/deliveries/cm8d3l1v3ry0000000000001/replay" \
  -H "Authorization: Bearer $LOCALOY_PROVIDER_KEY"
Response · 202
{
  "success": true,
  "message": "Replay queued. It carries the original event id, so a receiver that already processed this event will recognise it as a duplicate.",
  "data": {
    "id": "cm8d3l1v3ry0000000000003",
    "endpointId": "cm8wh00k0000000000000001",
    "partnerId": "cm1partnerid000000000000001",
    "endpointUrl": "https://hooks.example.com/localoy",
    "eventId": "evt_mfz3k2a1Xq9vT0bLm3Rk",
    "event": "booking.created",
    "status": "PENDING",
    "attempts": 0,
    "isTest": true,
    "…": "…"
  }
}