Skip to main content
Get an Event V2
Use this endpoint to retrieve one event together with every delivery and every attempt made for it. Each attempt records whether it was an original or a replay, when it ran, whether it succeeded, the response code, the response body (truncated to 200 characters and captured on failures), and the latency.
The Sphere-Delivery-Id header on a delivery you received is that delivery’s ID, so you can use it to line a request that hit your servers up against the delivery and attempt records here.
To re-send a delivery listed in the history, see replay a failed event delivery.

Authorizations

Authorization
string
header
required

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

Path Parameters

id
string
required

Response

The requested event, with its deliveries and delivery attempts.

attempts
object[]
required

Delivery attempts across the deliveries of this event

createdAt
string
required
deliveries
object[]
required

Deliveries of this event, one per subscribed endpoint

id
string
required
sequence
number | null
required
type
enum<string>
required
Available options:
*,
customer.*,
transfer.*,
document.*,
service.*,
customer.created,
customer.pending,
customer.approved,
customer.rejected,
transfer.created,
transfer.pendingFunding,
transfer.pendingReview,
transfer.fundsReceived,
transfer.processing,
transfer.succeeded,
transfer.returned,
transfer.pendingRefundInformation,
transfer.failed,
transfer.canceled,
transfer.refunded,
transfer.unexpectedError,
transfer.failedPrecondition,
transfer.expired,
transfer.unfunded,
document.pending,
document.processing,
document.verified,
document.rejected,
service.pending,
service.processing,
service.succeeded,
service.failed,
service.cancelled
Last modified on August 27, 2026