Webhook Deliveries

Retry every recent dead delivery

Once the consumer is fixed, replay everything the team dead-lettered since an instant in one call.

curl -X POST https://api.subscriby.net/v1/webhook-deliveries/retry-dead \
  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"since": "2026-09-05T22:00:00Z"}'

retried is how many rows were reset and queued. Only dead rows are touched: a failed row is still on its ladder and will be posted again on its own. The replay is capped at 500 rows per call so one request after a long outage cannot flood the queue or the target; call it again if the count comes back at the ceiling.

Each replayed row posts its event again, so confirm the consumer is healthy first; see replaying bulk dead deliveries.

post/v1/webhook-deliveries/retry-dead

Request

  • Base URL: https://api.subscriby.net
  • URL: https://api.subscriby.net/v1/webhook-deliveries/retry-dead
  • Auth: HTTP bearer

Headers

Idempotency-Keystring uuid required

A key unique to this operation, such as a fresh UUID. The same key replays the original 2xx response for 24 hours (with Idempotent-Replay: true), so a retry after a timeout never repeats the write; the same key with a different body is refused with 409.

Request body

sincestring date-time nullable

ISO 8601, not in the future. Only rows dead-lettered at or after this instant are replayed. Omit it for the last 24 hours.

Response

How many rows were re-queued and the instant the window opened at.

Example response

{
  "data": {
    "retried": 17,
    "since": "2026-09-05T22:00:00+00:00"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.