> ## Documentation Index > Fetch the complete documentation index at: https://docs.spherepay.co/llms.txt > Use this file to discover all available pages before exploring further. # Retrieve an Event with Full Delivery History > Retrieve an event by its ID. 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](/api-reference/events/replay). ## OpenAPI ````yaml openapi/spherepay.yaml GET /v2/events/{id} openapi: 3.0.0 info: contact: {} description: The Sphere REST API for payments, transfers, and accounts. title: Sphere API version: '2' servers: - description: Production url: https://api.spherepay.co security: - bearer: [] tags: [] paths: /v2/events/{id}: get: summary: Get an Event V2 description: Retrieve an event by its ID. operationId: getV2EventsById parameters: - in: path name: id required: true schema: type: string responses: '200': content: application/json: schema: properties: attempts: description: Delivery attempts across the deliveries of this event items: properties: attemptedAt: description: ISO 8601 timestamp when this attempt was made. example: '2026-01-01T00:05:00.000Z' type: string id: description: The unique identifier of the delivery attempt. example: atmpt_a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6 type: string latencyMs: description: >- Round-trip latency of this attempt in milliseconds, or null if no response was received. example: 128 nullable: true type: number responseBody: description: >- Response body returned by the endpoint, or null if no response was received. example: OK nullable: true type: string responseCode: description: >- HTTP status code returned by the endpoint, or null if no response was received. example: 200 nullable: true type: number success: description: Whether this attempt was delivered successfully. example: true type: boolean type: description: The kind of delivery attempt. enum: - original - replay - retry example: original type: string x-enumNames: - ORIGINAL - REPLAY - RETRY required: - id - type - attemptedAt - success - responseCode - responseBody - latencyMs type: object type: array createdAt: description: ISO 8601 timestamp when the event was created. example: '2026-01-01T00:00:00.000Z' type: string deliveries: description: Deliveries of this event, one per subscribed endpoint items: properties: attemptsUsed: description: Number of delivery attempts made so far. example: 1 type: number deliveredAt: description: >- ISO 8601 timestamp when the event was successfully delivered, or null if not yet delivered. example: '2026-01-01T00:05:00.000Z' nullable: true type: string id: description: The unique identifier of the delivery. example: eventDelivery_a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6 type: string latestAttempt: description: >- The most recent delivery attempt for this delivery, or null if no attempt has been made yet. nullable: true properties: responseCode: description: >- HTTP status code returned by the endpoint, or null if no response was received. example: 200 nullable: true type: number success: description: Whether this attempt was delivered successfully. example: true type: boolean type: description: The kind of delivery attempt. enum: - original - replay - retry example: original type: string x-enumNames: - ORIGINAL - REPLAY - RETRY required: - type - success - responseCode type: object status: description: The current status of this delivery. enum: - queued - delivering - delivered - failed example: delivered type: string x-enumNames: - QUEUED - DELIVERING - DELIVERED - FAILED webhookEndpointId: description: >- The unique identifier of the webhook endpoint this delivery targets. example: webhook_a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6 type: string required: - id - webhookEndpointId - status - attemptsUsed - deliveredAt - latestAttempt type: object type: array id: description: The unique identifier of the event. example: event_a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6 type: string sequence: description: >- Monotonically increasing sequence number for ordering events, or null if not assigned. example: 3 nullable: true type: number type: description: The type of the event. enum: - '*' - 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 example: transfer.succeeded type: string x-enumNames: - ALL - ALL_CUSTOMER - ALL_TRANSFER - ALL_DOCUMENT - ALL_SERVICE - CREATE_CUSTOMER - PENDING_CUSTOMER - APPROVE_CUSTOMER - REJECT_CUSTOMER - CREATE_TRANSFER - PENDING_FUNDING_TRANSFER - PENDING_REVIEW_TRANSFER - FUNDS_RECEIVED_TRANSFER - PROCESSING_TRANSFER - SUCCESSFUL_TRANSFER - RETURNED_TRANSFER - PENDING_REFUND_INFORMATION_TRANSFER - FAILED_TRANSFER - CANCELLED_TRANSFER - REFUNDED_TRANSFER - UNEXPECTED_ERROR_TRANSFER - FAILED_PRECONDITION_TRANSFER - EXPIRED_TRANSFER - UNFUNDED_TRANSFER - PENDING_DOCUMENT - PROCESSING_DOCUMENT - VERIFIED_DOCUMENT - REJECTED_DOCUMENT - PENDING_SERVICE - PROCESSING_SERVICE - SUCCESSFUL_SERVICE - FAILED_SERVICE - CANCELLED_SERVICE required: - id - type - createdAt - sequence - deliveries - attempts type: object description: The requested event, with its deliveries and delivery attempts. '400': content: application/json: examples: Bad Request: summary: Bad Request value: code: address/invalid correlationId: 28c61e885c6e5eaa78c1a2183a9b883c detail: Invalid request parameters status: 400 schema: $ref: '#/components/schemas/ProblemDetailsDto' description: Bad Request '404': content: application/json: examples: Not Found: summary: Not Found value: code: resource/not-found correlationId: 28c61e885c6e5eaa78c1a2183a9b883c detail: Resource not found status: 404 schema: $ref: '#/components/schemas/ProblemDetailsDto' description: Not Found '422': content: application/json: examples: Validation Error: summary: Validation Error value: code: validation/failed correlationId: 28c61e885c6e5eaa78c1a2183a9b883c detail: Validation failed errors: - detail: Invalid email format pointer: /email - detail: Name is required pointer: /name status: 422 schema: $ref: '#/components/schemas/ProblemDetailsDto' description: Unprocessable Entity - Validation Error components: schemas: ProblemDetailsDto: properties: code: type: string correlationId: type: string detail: type: string errors: items: properties: detail: type: string header: type: string parameter: type: string pointer: type: string required: - detail type: object type: array status: type: integer title: type: string required: - status - detail type: object securitySchemes: bearer: bearerFormat: JWT scheme: bearer type: http ````