Skip to main content
Replay an Event Delivery V2
Use this endpoint to re-send a delivery to its webhook endpoint. SpherePay makes exactly one automatic attempt per event per endpoint and never retries on its own, so recovering a delivery that failed while your endpoint was down is a deliberate call to this endpoint. The path takes the delivery ID, not the event ID. Find it on the delivery object returned by list events or in the full history from get event, or read it off the Sphere-Delivery-Id header of the original request. A replay re-sends the byte-for-byte identical payload with a fresh Sphere-Timestamp and Sphere-Signature, plus the headers Sphere-Delivery-Type: replay and Sphere-Replay-Reason: manual. Your verification code path is the same for originals and replays. A successful replay moves the delivery to delivered; a failed one leaves it failed and records another attempt. The attempt history is preserved either way.
Replays are delivered at-least-once on top of whatever your endpoint already received, and a delivery that already succeeded can be replayed. Deduplicate on the event id and apply the sequence staleness check so a replay is always safe to receive.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

eventDeliveryId
string
required

Response

The replay is queued for delivery. No content is returned; poll the event to observe the new attempt.

Last modified on August 27, 2026