[
""
][
null
][
null
][
null
][
null
]List transactions for many payment credentials in one call
Distinct transactions touching any address under each of up to 25 payment credentials, newest first, within an optional slot window. The limit applies PER CREDENTIAL, not to the response as a whole, so one busy credential cannot crowd the others out of the batch. Every requested credential appears in the response, in request order, with an empty transactions array when it has no history in the window. Served by cardano-db-sync direct SQL where a db-sync datasource is configured for the network, and by YACI elsewhere. On the db-sync path the whole batch is ONE query, so it is bounded by one query timeout rather than one per credential; a batch containing a credential busy enough to exceed that timeout returns 504 for the whole batch, so split such a credential into its own request.
[
""
][
null
][
null
][
null
][
null
]Authorizations
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
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.
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 Transactions per credential, applied to each credential independently
Body
Bulk payment-credential lookup request
Payment credential hashes, 56 hex chars each, max 25 per call
25^[0-9a-fA-F]{56}$[
"87be75696aea59b41b36415d0b7c8b7a0c21fe3dd5a63939acfbc3a0"
]
Response
Transactions per credential
The payment credential exactly as it appeared in the request
"87be75696aea59b41b36415d0b7c8b7a0c21fe3dd5a63939acfbc3a0"
Distinct transactions touching any address under the credential, newest first, capped at the request's limit for this credential alone. Empty when the credential has no history in the window.
Show child attributes
Show child attributes