Skip to main content
GET
List transactions for a payment credential

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

credential
string
required
Pattern: ^[a-fA-F0-9]{56}$

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
fromSlot
integer<int64>
toSlot
integer<int64>
page
integer<int32>
default:1
Required range: 1 <= x <= 1000
pageSize
integer<int32>
default:100
Required range: 1 <= x <= 100

Response

Transactions retrieved

txHash
string
slot
integer<int64>
blockHeight
integer<int32>
blockTime
integer<int64>
epoch
integer<int32>