Skip to main content
GET
cURL

Headers

Authorization
string
required

Bearer token. Format: Bearer <api_key>

Path Parameters

transactionId
string
required

Transaction identifier.

Response

The request has succeeded.

A transaction, discriminated by type. Use the type field to narrow the details payload — each variant has a different shape. The envelope (status, amount, asset, fee, timestamps) is uniform across variants.

Variants:

  • CRYPTO_PAYINdetails is TransactionCryptoPayinDetails
  • CRYPTO_PAYOUTdetails is TransactionCryptoPayoutDetails
  • FIAT_PAYINdetails is TransactionFiatPayinDetails
  • FIAT_PAYOUTdetails is TransactionFiatPayoutDetails
  • TRADEdetails is TransactionTradeDetails
  • TRANSFERdetails is TransactionTransferDetails
  • NXOSNET_TRANSFERdetails is TransactionNxosnetTransferDetails
  • ADJUSTMENTdetails is TransactionAdjustmentDetails
  • COMMISSIONdetails is TransactionCommissionDetails
object
enum<string>
required

Object type. Always transaction.

Available options:
transaction
transactionId
string
required

Unique transaction identifier.

accountId
string
required

Account this transaction belongs to. Always one of your organization's accounts (the listing query enforces ownership).

status
enum<string>
required

Current status. See TransactionStatus for transitions.

Available options:
EXPECTED,
LOCKED,
COMPLETED,
DECLINED,
REFUNDED
description
string | null
required

Optional human-readable description.

tags
string[]
required

Free-form tags set at create time (e.g. ["crypto_payout", "ethereum_mainnet"]).

amount
string | null
required

Primary amount in major units. For most types this is the amount the customer's account moved by. For TRADE this is null — trades have two distinct assets in play; see details.from and details.to instead.

asset
string | null
required

Asset code of the primary amount. Null for TRADE — see details.from / details.to.

fee
object
required

Service-fee breakdown. Always populated; every component is zero when no service fee applied. Note: trade spread fees are NOT here — they live in details.spread on TRADE transactions.

Example:
createdAt
string
required

When the transaction was created (platform clock).

updatedAt
string
required

When the transaction was last updated.

type
enum<string>
required
Available options:
CRYPTO_PAYIN
details
object
required

Crypto deposit details — the on-chain receipt that funded the account.