Skip to main content
GET
List transaction history

Authorizations

X-Api-Key
string
header
required

API key (programmatic access — recommended)

Send your API key in the X-Api-Key header. Keys start with nxs_ and are created in the dashboard (or via POST /api/keys with a session JWT).

Each key is scoped to one chain and one network (for example CARDANO_MAINNET), fixed at creation time. It cannot query a different network on the same chain, and it cannot query a different chain at all. A mismatched network parameter returns 400 Network Mismatch. Create one key per chain and network under the same account.

This is the credential most integrations should use.

Path Parameters

address
string
required

Query Parameters

before
string

Return transactions older than this signature

until
string

Return transactions newer than this signature

limit
integer<int32>

Page size, 1-1000 (default 50)

Required range: 1 <= x <= 1000
network
enum<string>

Accepts either the value listed here (CARDANO_MAINNET) or its kebab-case alias (cardano-mainnet); matching is case-insensitive. Omit it and the network is taken from the API key. A value that disagrees with the key's own network returns 400 Network Mismatch.

Available options:
CARDANO_MAINNET,
CARDANO_PREPROD,
CARDANO_PREVIEW,
MIDNIGHT_MAINNET,
MIDNIGHT_PREPROD,
MIDNIGHT_PREVIEW,
MIDNIGHT_STAGENET,
BITCOIN_MAINNET,
BITCOIN_TESTNET4,
SOLANA_MAINNET,
SOLANA_DEVNET

Response

200 - */*

OK

signature
string

Transaction signature (base58, 64 bytes)

slot
integer<int64>

Slot the transaction landed in

Example:

312345678

blockTime
integer<int64> | null

Block time, Unix seconds; null when unknown

Example:

1731456000

success
boolean

False when the transaction failed (it still paid its fee)

fee
integer<int64> | null

Fee in lamports; null when the RPC fallback answered

Example:

5000