Overview
The NFTX v4 API — a read-only REST interface for reading collections, listings, activity, prices, portfolios, and swap quotes.
The NFTX v4 API is a read-only REST interface over the protocol. Use it to read collection data, listings, activity, holders, prices, and user portfolios, and to fetch swap quotes and transaction calldata your own wallet then submits. It's the fastest way to build on NFTX without indexing the chain yourself.
Base URL and chains
Every protocol route is scoped to a chain:
/v1/{chain}/...{chain} is a numeric chain ID or one of its slug aliases. The API supports:
Ethereum Mainnet
1
mainnet, ethereum, eth
Arbitrum One
42161
arbitrum, arbitrum-one, arb, arb-mainnet
Ink
57073
ink, ink-mainnet
Robinhood Chain
4663
robinhood, robinhood-chain, rh
Ethereum Sepolia (testnet)
11155111
sepolia, eth-sepolia, ethereum-sepolia
Robinhood Chain Testnet (testnet)
46630
robinhood-testnet, robinhood-chain-testnet, rh-testnet
For example, listing collections on Robinhood Chain is GET /v1/4663/collections, and on Ethereum Mainnet GET /v1/1/collections (or GET /v1/ethereum/collections).
What's inside
Health, readiness, protocol config and stats
Collection data, tokens, holders, traits, prices, liquidity
Global, collection-, token-, and user-scoped activity feeds
Liquid and Dutch listings for a collection or a single token
Search across collections and tokens
Portfolio, balances, listings, escrow, votes, positions
Quotes, approval checks, and executable swap calldata
Streaming protocol events
Vault creation preflight checks
Test-token metadata and images (testnet)
About this spec
The reference below is generated live from the NFTX v4 API's OpenAPI specification, served at nftx-v4-api-production.up.railway.app/openapi.json. The API service emits this spec via its openapi:emit build step, so the reference stays in step with the deployed API.
Last updated
Was this helpful?