Get Transaction
Single transaction by id.
Authorizations
Paste your Connect API key (sk_live_… for production, sk_test_… for sandbox) without the Bearer prefix. Mint and rotate keys from the admin panel.
Path Parameters
Response
Successful Response
A single transaction row in the partner-facing shape.
All amounts are decimal strings (JS Number boundary defense). Optional fields are omitted from the JSON when None — we use Pydantic's exclusion-on-None pattern for that, configured at serialization time in the handler.
Transaction id (UUID).
Derived from the internal row's direction and is_external flag; see schema docstring for the mapping.
deposit, payout, transfer, conversion, ramp Partner-facing status. The full internal state machine (pending/processing/completed/failed/rejected/canceled) is collapsed into three buckets matching the spec.
pending, confirmed, failed Asset code, uppercase (USDT, XAUT).
Asset amount as a decimal string.
The partner's user id, echoed back. Set for both deposit (recipient is the partner's user) and payout (sender is the partner's user). For internal transfers, the ref of whichever side is the partner's user; None if neither side is mapped (shouldn't happen in a tenant-scoped query, defensive against schema drift).
Network code (lowercase). NULL on internal-only ledger transfers (is_external=false) where no chain was touched.
On-chain sender address. NULL on internal transfers and on outgoing rows where we have no on-chain metadata yet.
On-chain destination address. NULL on internal transfers.
Blockchain transaction hash. NULL until broadcast (pending state) and on internal transfers.
When the transaction reached a terminal state (confirmed or failed). NULL while pending.