Skip to main content
GET
/
v1
/
transactions
/
{transactionId}
cURL
curl --request GET \
  --url https://api.nxos.io/v1/transactions/{transactionId} \
  --header 'Authorization: <authorization>'
{
  "object": "transaction",
  "transactionId": "<string>",
  "accountId": "<string>",
  "status": "EXPECTED",
  "description": "<string>",
  "tags": [
    "<string>"
  ],
  "amount": "<string>",
  "asset": "<string>",
  "fee": {
    "fixed": "50.00",
    "bps": 0,
    "bpsAmount": "0.00",
    "total": "50.00",
    "asset": "USD"
  },
  "createdAt": "<string>",
  "updatedAt": "<string>",
  "type": "CRYPTO_PAYIN",
  "details": {
    "chainName": "<string>",
    "chainTransactionId": "<string>",
    "fromAddress": "<string>",
    "toAddress": "<string>",
    "blockHeight": 123,
    "blockTimestamp": "<string>"
  }
}

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_PAYIN → details is TransactionCryptoPayinDetails
  • CRYPTO_PAYOUT → details is TransactionCryptoPayoutDetails
  • FIAT_PAYIN → details is TransactionFiatPayinDetails
  • FIAT_PAYOUT → details is TransactionFiatPayoutDetails
  • TRADE → details is TransactionTradeDetails
  • TRANSFER → details is TransactionTransferDetails
  • NXOSNET_TRANSFER → details is TransactionNxosnetTransferDetails
  • ADJUSTMENT → details is TransactionAdjustmentDetails
  • COMMISSION → details 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
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:
{
  "fixed": "50.00",
  "bps": 0,
  "bpsAmount": "0.00",
  "total": "50.00",
  "asset": "USD"
}
​
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.