Skip to main content
GET
List transaction hashes for a Cardano address

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
Required string length: 1 - 200
Pattern: ^[a-zA-Z0-9_]+$

Query Parameters

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,
APEX_PRIME_MAINNET,
APEX_VECTOR_MAINNET,
APEX_VECTOR_TESTNET,
MIDNIGHT_MAINNET,
MIDNIGHT_PREPROD,
MIDNIGHT_STAGENET,
BITCOIN_MAINNET,
BITCOIN_TESTNET4
page
string
default:""

Page number (1-based)

pageSize
string
default:""

Number of items per page

fromBlockHeight
string
default:""

Only return transactions at or after this block height

toBlockHeight
string
default:""

Only return transactions at or before this block height

order
string
default:""

Order of results: asc (oldest first, default) or desc

Response

Transactions on the address.

txHash
string
txIndex
integer<int32>
blockHeight
integer<int64>
blockTime
integer<int64>
epochNo
integer<int32>
slot
integer<int64>
input
boolean
output
boolean