Get a Transaction by ID
Retrieve one settled transaction by id, with its per-leg breakdown. Each leg carries a direction (FROM_AGORA or TO_AGORA) and a rail-specific detail keyed by type: token (transactionHash), wire (Fedwire imad), bookTransfer, or instantPayment (confirmationNumber). A fee leg is a manual accounting entry and carries no rail reference. A 404 means no such transaction exists for your organization.
Authentication
Session JWT from POST /v0/auth/token, sent as Authorization: Bearer <sessionJwt>.
See Authentication for more details.
Path parameters
Response
Stable UUID identifying this transaction; pass to the detail endpoint to fetch legs.
ISO-8601 timestamp of the first leg.
True if this transaction used Agora's instant-settlement path rather than standard settlement.
Number of customer-facing legs in this transaction.
ISO-8601 timestamp when the transaction settled. Null until settled.
Lifecycle status. v1 emits only "settled". This is an open, extensible enum; future values (e.g. pending) may appear, so clients must tolerate unknown values.
Customer-facing transaction type: mint, redeem, bridge, reward, or return. Treated as an open enum; tolerate unknown values.
The customer-facing legs that make up this transaction.

