Skip to main content
GET
Asset Information

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.

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
assetPolicy
string
required
Minimum string length: 1
Pattern: ^[a-fA-F0-9]{1,64}$
assetName
string
required
Minimum string length: 1
Pattern: ^[a-fA-F0-9]{0,64}$

Response

Asset Information retrieved

asset
string
policyId
string
assetName
string
assetNameAscii
string
fingerprint
string
quantity
string
initialMintTxHash
string
mintCnt
integer<int32>
burnCnt
integer<int32>
mintOrBurnCount
integer<int32>
creationTime
integer<int64>
onchainMetadata
string
cip68Metadata
string
metadata
object
latestMintTxHash
string
latestMintTime
integer<int64>
holdersByAddress
integer<int64>
holdersByAccount
integer<int64>
{key}
any