> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # Get event delivery > Returns a single event_delivery row plus its attempt history. Lookups for unknown ids surface as not-found (SPB-0010), byte-identical to truly-missing. ## OpenAPI ````yaml en/openapi/v3-current/spb.yaml get /v1/str/event-deliveries/{deliveryId} openapi: 3.1.0 info: contact: email: contact@lerian.studio name: Lerian Studio url: https://lerian.studio description: >- OpenAPI 3.1 surface for Lerian SPB, the direct integration between the institution and the Brazilian Payment System (SPB) over the National Financial System Network (RSFN). It covers the Reserve Transfer System (STR): message registry and capability catalog, operation lifecycle (bank transfers, IBS repasses, liquidity transfers, returns and cancellations), reserve-account and schedule queries, alçada governance, reconciliation, and event delivery. license: name: Lerian Studio General License title: Lerian SPB API version: 1.0.0 servers: - url: https://spb.sandbox.lerian.net security: [] tags: - description: Immutable audit-record trails for STR operations and lifecycle events. name: Audit - description: >- STR capability catalog describing supported message types and their constraints. name: Capabilities - description: >- ICP-Brasil certificate inventory with hot-reloadable rotation and activation. name: Certificates - description: >- Maker-checker approval queue for emissions parked above their alçada band: list pending, sign (approve), and deny. name: EmissionApprovals - description: Webhook event-delivery records with retry control for failed dispatches. name: EventDeliveries - description: Operation event catalog enumerating the emitted domain event types. name: Events - description: >- Inbound GEN-family notice log (GEN0001 connectivity echo, GEN0004 transmission error, GEN0005 administrative notice). name: GenNotices - description: >- SPB alçada governance: the value-band table and per-message-type signature requirements, hot-reloaded at runtime. name: Governance - description: >- Read raw STR message status: list messages and read a single message by NUOp. name: Messages - description: Aggregated operational summaries and metrics across STR operations. name: OperationalIntelligence - description: >- STR operation lifecycle for bank transfers and IBS repasses, including returns and cancellations. name: Operations - description: >- Service readiness state covering startup self-probes and dependency health. name: Readiness - description: Reconciliation cases and the actions that resolve operation discrepancies. name: Reconciliation - description: >- STR reports suite: synchronous, date-ranged aggregate reports (financial movement, rejected transactions, volumetria) over Lerian SPB's own transmission record. name: Reports - description: >- STR0013 reserve-account balance and STR0014 statement (extrato, message-mode) queries and their async results. name: ReserveQueries - description: >- GEN0019 participant responsável roster: full-replacement updates announced to BACEN. name: Responsibles - description: STR operating-window schedule governing when operations may be sent. name: Schedule - description: >- STR0001 single-party schedule queries (consulta de horários do STR) and their async STR0001R1 grid results. name: ScheduleQueries - description: Runtime SPB configuration settings for the STR integration. name: Settings - description: Webhook endpoint registration and management for event delivery. name: Webhooks - description: >- Flow (mandatory order): certificate → readiness → connectivity-test → submit. Activate a certificate, confirm the rail reports ready, pass a connectivity test, then submit an operation. Each step is its own resource; a submit must not be attempted before readiness passes. name: onboarding - description: >- Flow (mandatory order): parent operation SETTLED → return/cancel. A return or cancellation is a sub-resource of a settled parent operation; the {operationId}/{endToEndID} path segment enforces the parent structurally. name: lifecycle paths: /v1/str/event-deliveries/{deliveryId}: get: tags: - EventDeliveries summary: Get event delivery description: >- Returns a single event_delivery row plus its attempt history. Lookups for unknown ids surface as not-found (SPB-0010), byte-identical to truly-missing. operationId: getEventDelivery parameters: - description: Delivery UUID. in: path name: deliveryId required: true schema: description: Delivery UUID. examples: - 550e8400-e29b-41d4-a716-446655440010 type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/EventDeliveryEnvelope' description: OK default: content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Error security: - BearerAuth: [] components: schemas: EventDeliveryEnvelope: additionalProperties: false properties: attempts: description: Chronological attempt history for the delivery. items: $ref: '#/components/schemas/EventDeliveryAttemptResponse' type: - array - 'null' correlationId: description: >- Request-scoped correlation identifier echoing X-Request-ID, for pivoting from response to trace. examples: - 550e8400-e29b-41d4-a716-446655440004 type: string delivery: $ref: '#/components/schemas/EventDeliveryResponse' description: The event delivery record. required: - delivery - attempts - correlationId type: object Detail: additionalProperties: false properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). examples: - ERR-0001 type: string detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string type: object EventDeliveryAttemptResponse: additionalProperties: false properties: attemptNumber: description: 1-based ordinal of this attempt within the delivery. examples: - 1 format: int64 type: integer attemptedAt: description: RFC3339 UTC timestamp when this attempt was made. examples: - '2026-06-14T12:00:00Z' type: string deliveryAttemptId: description: Delivery attempt UUID. examples: - 550e8400-e29b-41d4-a716-446655440020 type: string deliveryId: description: UUID of the delivery this attempt belongs to. examples: - 550e8400-e29b-41d4-a716-446655440010 type: string errorSummary: description: >- Summary of the failure for this attempt; omitted when the attempt succeeded. type: string responseStatus: description: >- HTTP status code returned by the webhook endpoint; omitted when no response was received (e.g. connection error). examples: - 200 format: int64 type: integer status: description: Outcome status of this individual attempt. examples: - DELIVERED type: string required: - deliveryAttemptId - deliveryId - attemptNumber - status - attemptedAt type: object EventDeliveryResponse: additionalProperties: false properties: attempts: description: Number of delivery attempts made so far. examples: - 1 format: int64 type: integer createdAt: description: RFC3339 UTC timestamp when the delivery record was created. examples: - '2026-06-14T12:00:00Z' type: string deliveryId: description: Event delivery UUID. examples: - 550e8400-e29b-41d4-a716-446655440010 type: string eventId: description: UUID of the control-plane event being delivered. examples: - 550e8400-e29b-41d4-a716-446655440011 type: string eventType: description: Canonical control-plane event type being delivered. examples: - str.operation.accepted type: string lastAttemptAt: description: >- RFC3339 UTC timestamp of the most recent attempt; omitted before the first attempt. examples: - '2026-06-14T12:00:00Z' type: string lastError: description: >- Summary of the most recent delivery error; omitted when the last attempt succeeded. type: string nextRetryAt: description: >- RFC3339 UTC timestamp when the next retry is scheduled; omitted when no retry is pending. examples: - '2026-06-14T12:00:00Z' type: string operationId: description: >- UUID of the related operation when the event is operation-scoped; omitted otherwise. examples: - 550e8400-e29b-41d4-a716-446655440013 type: string status: description: 'Delivery status: PENDING, DELIVERED, FAILED, RETRYING, or EXHAUSTED.' examples: - DELIVERED type: string updatedAt: description: RFC3339 UTC timestamp of the last delivery-record update. examples: - '2026-06-14T12:00:00Z' type: string webhookId: description: UUID of the destination webhook endpoint. examples: - 550e8400-e29b-41d4-a716-446655440012 type: string required: - deliveryId - eventId - webhookId - eventType - status - attempts - createdAt - updatedAt type: object ErrorDetail: additionalProperties: false properties: location: description: >- Where the error occurred, e.g. 'body.items[3].tags' or 'path.thing-id' type: string message: description: Error message text type: string value: description: The value at the given location type: object securitySchemes: BearerAuth: bearerFormat: JWT description: JWT bearer token issued by the identity provider. scheme: bearer type: http ````