Skip to main content
POST
Get UTXOs by references

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

Body

application/json
txHash
string
default:""
required

Transaction hash containing the UTXO

Required string length: 64
Pattern: ^[a-fA-F0-9]{64}$
Example:

"8f83b73e8e7f4b7d8f9c2e8f83b73e8e7f4b7d8f9c2e8f83b73e8e7f4b7d8f9c"

outputIndex
integer<int32>
default:""
required

Output index within the transaction (0-based)

Required range: x >= 0
Example:

0

Response

OK

collateral
boolean
reference
boolean
tx_hash
string
output_index
integer<int32>
owner_addr
string
owner_stake_addr
string
owner_payment_credential
string
owner_stake_credential
string
amounts
object[]
lovelace_amount
integer<int64>
data_hash
string
inline_datum
string
inline_datum_json
object
reference_script_hash
string
script_ref
string
block_number
integer<int64>
block_time
integer<int64>
slot
integer<int64>
block_hash
string
epoch
integer<int32>
consumed_by_tx
string
is_collateral_return
boolean
{key}
any