Skip to main content
GET
Address UTXOs filtered by asset

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_]+$
asset
string
required
Required string length: 56 - 120
Pattern: ^[a-fA-F0-9]+$

Query Parameters

network
enum<string>
Available options:
CARDANO_MAINNET,
CARDANO_PREPROD,
CARDANO_PREVIEW,
APEX_PRIME_MAINNET,
APEX_VECTOR_MAINNET,
APEX_VECTOR_TESTNET,
MIDNIGHT_MAINNET,
MIDNIGHT_PREPROD,
MIDNIGHT_PREVIEW,
BITCOIN_MAINNET,
BITCOIN_TESTNET4
page
string
default:""

Page number (1-based)

pageSize
string
default:""

Number of items per page

Response

UTXOs of the address

txHash
string
txIndex
integer<int32>
address
string
stakeAddress
string
paymentCred
string
epoch
integer<int32>
blockHeight
integer<int32>
blockTime
integer<int32>
slot
integer<int64>
value
string
datumHash
string
inlineDatum
object
referenceScript
object
assets
object[]
spent
boolean
blockHash
string
cborHex
string