Replay failed deliveries

POST

/v1/webhooks/{webhook_id}/replay

curl -X POST "https://us1.platform.bird.com/v1/webhooks/{webhook_id}/replay" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "since": "2026-05-07T00:00:00Z",
    "until": "2026-05-07T23:59:59Z"
  }'

Queues redelivery of deliveries that failed. The window runs from since (default: the last 24 hours) to until, and events the endpoint already received successfully are skipped, so a replay never double-delivers.

Only failed attempts are replayed. An event the endpoint was never sent, such as one that arrived while it was paused, has no failed attempt to replay, so a replay does not recover it.

The 202 response means the replay is queued. Events are redelivered asynchronously and retried like any other delivery; no count or task ID is returned, so track results with List delivery attempts.

Replays are limited to 20 per organization per UTC day; beyond that the request returns a 429 WebhookReplayQuotaExceeded.

Parameters

webhook_id

string

ID of the webhook endpoint (whk_ prefix), as returned when it was created.

Request Payload

since

string

Replay events that occurred at or after this timestamp. Defaults to 24 hours before the request when omitted.

until

string

Replay events that occurred before or at this timestamp. Omit to bound the window only by since.

Related resources

Continue with the documentation, guides and examples for this topic. Resources are in English.

Watch the guideWebhooks done right: reliable delivery events Understand the conceptHow do I verify a webhook signature?Follow the learning pathOperate messaging reliably Implementation guideWebhooks & events

Try the practice and get an implementation brief

curl -X POST "https://us1.platform.bird.com/v1/webhooks/{webhook_id}/replay" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "since": "2026-05-07T00:00:00Z",
    "until": "2026-05-07T23:59:59Z"
  }'