Skip to main content
POST
Enqueues up to 100 matching retained deliveries, ordered by created_at then delivery ID, for asynchronous re-delivery and returns 202 Accepted. The request returns after replay work is saved; delivery workers perform the attempts as capacity becomes available. Provide at least one filter. Each re-delivery keeps its original event_id, so receivers dedupe.

Body Parameters

Provide at least one:
string
Re-deliver all deliveries of one logical event (across endpoints).
string
Re-deliver deliveries for one endpoint.
string
Re-deliver deliveries in a state: pending, delivered, failed, dead.
string
Lower bound on created_at (ISO-8601, timezone-aware).
string
Upper bound on created_at (ISO-8601, timezone-aware).
string
Opaque next_cursor from the previous response, at most 256 characters. Keep the same filters. Omit or pass null to start from the beginning; the cursor alone does not count as a filter.
A delivery whose endpoint is inactive is skipped (not an error). A delivery with a fresh pending retry or replay is also skipped. Replay is at-least-once: repeating a request after that work completes can request another attempt, so receivers must deduplicate by event_id.

Examples

requested counts the selected deliveries; requeued, skipped, and failed count their acceptance outcomes and sum to requested. Acceptance does not mean your receiver returned 2xx. truncated is true when more than 100 deliveries matched after the cursor. last_created_at is the created_at of the last selected delivery, or null when none matched. When truncated is true, send next_cursor as the next request’s cursor with the original filters. It advances exclusively past the last selected delivery, including skipped and failed rows, even when many deliveries share a timestamp. next_cursor is null on the final or empty page. A cursor remains valid if the boundary delivery is deleted. It is bound to the account and normalized filters; changing either returns 400 validation_failed.
Bulk replay is capped at 100 per call and rate-limited per account. Both date bounds remain inclusive. last_created_at is informational; using it as date_from repeats the boundary timestamp. Use cursor to continue, and keep any original date bounds unchanged.Pagination is not a snapshot. Each page evaluates the current filters: deliveries whose state changes may enter or leave the selection, and newly inserted rows before the cursor are not revisited. Completed earlier pages are not selected again when you continue with the cursor. Use a fixed date_to to bound a recovery window and inspect delivery history for skipped or failed rows.
Replay targets the original active endpoint even if its event subscriptions have changed. Deleted, missing, or disabled endpoints are skipped. After fixing a disabled destination, explicitly re-enable it before replaying retained history.

Error Codes