Recover events a webhook endpoint missed
Queues a delivery for every subscribed event created since since that never reached this endpoint, for example while it was disabled, and the next attempt for every event whose attempts to it all failed with no retry pending. Events that reached the endpoint or still have an attempt pending are left alone. since is clamped to the endpoint’s creation time and must be within the last 30 days. The work runs in batches so a large window never ties up one transaction; a resent event gets one more attempt. Deliveries start within about a minute, in the order the dispatcher’s sweep picks them up.
Authorizations
Use Authorization: Bearer end_sk_* for partner API keys (e.g. end_sk_AbCd_example_api_key).
Headers
Unique key that makes this request safe to retry. Replaying the key with the same body returns the original response with Idempotent-Replayed: true; replaying it with a different body returns 409 idempotency.key_conflict.
1 - 255"a1b2c3d4-0000-4000-8000-000000000000"
Path Parameters
"8e1a7f50-90ab-4cde-8012-3456789abcde"
Body
Queue every subscribed event created at or after this time that never reached the endpoint. At most 30 days ago.
"2026-09-22T00:00:00Z"
Response
How many events were queued, split by missed and failed.
The time recovery started from: the requested since, or the endpoint's creation time when that is later.
Attempts inserted by this call, missed plus failed. They arrive over the following minutes; follow them through the events list filtered by endpoint_id.
x >= 0Events that had never been attempted to this endpoint.
x >= 0Events whose attempts to this endpoint had all failed with no retry pending; each gets its next attempt.
x >= 0
