Skip to main content
This endpoint returns the complete event history for a given transaction, listing every status change in chronological order. Each event record describes a discrete state transition — for example, from PENDING to PROCESSING to PAID. This audit trail is invaluable for debugging payment flows, reconciling records, and investigating disputes or unexpected transaction outcomes.

Endpoint

GET https://v2.certopaybrasil.com/api/transaction-events/transaction/{transactionId}

Authentication

All requests must include your secret API key in the X-Api-Key header.
X-Api-Key
string
required
Your CertoPay secret API key (e.g. sk_live_sua_chave_aqui).

Path Parameters

transactionId
string
required
The unique UUID of the transaction whose event history you want to retrieve. Obtain this from the List Transactions or Get Transaction endpoints.

Example Request

curl https://v2.certopaybrasil.com/api/transaction-events/transaction/uuid-da-transacao \
  -H "X-Api-Key: sk_live_sua_chave_aqui"

Response

Returns an array of event objects, ordered chronologically from oldest to newest. Each object describes a single status transition for the transaction.

200 — Success

[
  {
    "id": "uuid-do-evento",
    "transactionId": "uuid-da-transacao",
    "type": "transaction.created",
    "status": "PENDING",
    "createdAt": "2026-06-26T10:00:00Z"
  },
  {
    "id": "uuid-do-evento-2",
    "transactionId": "uuid-da-transacao",
    "type": "transaction.paid",
    "status": "PAID",
    "createdAt": "2026-06-26T10:05:00Z"
  }
]

Response Fields

id
string
Unique identifier (UUID) for this individual event record.
transactionId
string
UUID of the transaction this event belongs to.
type
string
The event type describing what occurred (e.g. transaction.created, transaction.paid, transaction.failed).
status
string
The transaction status at the time this event was recorded (e.g. PENDING, PROCESSING, PAID, FAILED).
createdAt
string
ISO 8601 timestamp for when this event was recorded.
The event list is ordered chronologically — the first item represents the earliest recorded state and the last item represents the most recent. This makes it easy to trace the full lifecycle of a payment from creation to completion or failure. Use this endpoint alongside Webhook Delivery History for comprehensive payment flow auditing.