Fetch a transaction
Same shape as one row of the list. Resolves ids from both spaces. A transaction that is not yours is a 404, never a 403: the difference between those two answers would itself tell you which ids exist.
Authorization
KeyID Timestamp Nonce Signature Your key id, gyv_k_live_... or gyv_k_sandbox_....
In: header
Unix seconds. Must be within 5 minutes of our clock.
In: header
A unique value per request. Replays are rejected.
In: header
Ed25519 signature over the canonical string. See the Signing guide.
In: header
Path Parameters
uuidResponse Body
application/json
application/json
application/json
curl -X GET "https://example.com/transactions/497f6eca-6276-4993-bfeb-53cbbbba6f08"{ "data": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "direction": "in", "status": "successful", "currency": "USDC", "decimals": 6, "amount": "20.000000", "amount_minor": "20000000", "fee": "0.600000", "fee_minor": "600000", "net": "19.400000", "net_minor": "19400000", "created_at": "2019-08-24T14:15:22Z", "reference": "WDR_TBJWZFYIYTM3KPF5", "chain": "ethereum", "network": "onchain", "address": "string", "hash": "string", "invoice": "string", "payment_hash": "string", "address_reference": "string", "address_label": "string", "completed_at": "2019-08-24T14:15:22Z", "failure_code": "transfer_failed", "failure_message": "string", "settlement_currency": "GHS", "settlement_decimals": 0, "settlement_amount": "string", "settlement_amount_minor": "string", "rate": "string", "destination": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "type": "string", "country": "string", "network": "string", "account_masked": "string", "rail": "momo" } }}The Transaction object
One money movement. Fields marked *(in)* appear only on inbound rows and *(out)* only on outbound ones; a field with nothing to say is omitted rather than sent empty.
Fetch a transaction by reference
Same shape as one row of the list, looked up by the handle we print and webhook rather than by our uuid - `DEP_…` for a deposit, `WDR_…` for a payment. Use this when what you hold came off a webhook, a receipt or a support thread. Both spaces are searched whatever the prefix, so a deposit from before September 2026 (`CTX_`/`LNX_`) still resolves. Not every transaction has one: a direct on-chain receive mints no movement row and so has no reference. Those are reachable by `id` only.