Replay Deliveries in a Range
Re-sends the webhook’s past deliveries within a time window, optionally limited to specific events or to failed deliveries. Use it to recover events your endpoint missed. The replay runs asynchronously and nothing about it is stored: each re-send appears as a new entry in the webhook’s delivery log. Each matching message is re-sent once, with its original webhook-id unless you pass regenerate_ids. Only available for enabled webhooks on API version v1; deliveries are retained for 30 days.
Autorisations
An Account API key, an App API key, an account access token, or an account-scoped user token. Prepend the key or token with Bearer, for example Bearer ***************************. See Auth & API keys for how to get each one.
En-têtes
A unique key that makes this request safe to retry. See Idempotent requests.
255"d9105228-4a08-46b1-8b91-42fed586d383"
Corps
Only replay messages whose most recent delivery attempt in the window failed. Defaults to false. Best-effort: a message whose attempts span processing batches can still be re-sent — replays keep the original webhook-id by default, so consumers that deduplicate are unaffected.
true
Re-send each replayed message under a freshly generated webhook-id (in both the envelope and the signed headers) instead of its original one. Defaults to false. Use this when your endpoint deduplicates on webhook-id and you want it to process the replays as new messages.
true

