Skip to main content
GET
Get inscriptions held at address, with UTXO context

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: 14 - 128
Pattern: ^[a-zA-HJ-NP-Z0-9]{14,128}$

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
cursor
string
Maximum string length: 256
limit
integer<int32>
Required range: 1 <= x <= 100

Response

200 - */*

OK

Paged inscriptions held at an address

address
string
data
object[]
nextCursor
string
default:""

Opaque cursor for the next page; absent when exhausted. Best-effort stable: the holding set can change between pages.