Testnet
The XRP Ledger Testnet, indexed the way Mainnet is: tokens with holders, order books, trades and 5-minute candles, accounts, AMM pools, NFTs, offers, collections and their history — read from our own Testnet node. No key needed. Ids are the Mainnet ones: a token is md5(issuer_currency), a collection is issuer:taxon.
Start at GET /v1/testnet/fixtures: it names live accounts, a busy token, an NFT with offers and one of every ledger object that xrpl.to keeps alive on Testnet, plus a real transaction of every type. Testnet resets without warning; the data is rebuilt from the chain within minutes, and only objects touched since count. Open the Testnet sandbox →
Testnet
- GET
/v1/testnet/fixturesWhat the simulation keeps alive on Testnet: live accounts, its tokens (tokens[]: name, currency, issuer, holders, amm, role — stablecoin | deep (the high-liquidity pool) | volatile (a thin pool, swung every round) | crowd — with a note saying what each does, and peg_usd on the stablecoin), its collections (collections[]: name, issuer, taxon, role blue-chip | drop, note, items), an NFT with offers, one of every ledger object, and a real transaction of each type (catalogue[]: id, kind, about, result, hash, and tx — the JSON it sent, without fee, sequence, expiry or signature, a working template for that variation) — start here - GET
/v1/testnet/healthBoth collectors' head ledger against the network, and whether that is current - GET
/v1/testnet/tokensTestnet tokens. tvl is the token's XRP pool valued on both sides (twice its XRP reserve); a token with no XRP pool has none - GET
/v1/testnet/tokens/{md5}A Testnet token with its AMM pool - GET
/v1/testnet/tokens/{md5}/holdersHolders of a Testnet token, largest first - GET
/v1/testnet/tokens/{md5}/offersThe order book of a Testnet token against XRP - GET
/v1/testnet/tokens/{md5}/tradesFills of a Testnet token, newest first - GET
/v1/testnet/tokens/{md5}/ohlc5-minute candles of a Testnet token - GET
/v1/testnet/accounts/{address}A Testnet account as the collector last saw it, with its trust lines, resting offers and last 20 trades - GET
/v1/testnet/ammTestnet AMM pools, deepest first. A pool of two tokens has token and token2 (in a fixed order, by code) and xrp 0; its spot is token2 per token - GET
/v1/testnet/amm/{account}A Testnet AMM pool by its account - GET
/v1/testnet/nft/collectionsTestnet NFT collections, by issuer and taxon. volume/sales are all-time XRP sales; vol24h/sales24h the last 24 h, recounted every minute - GET
/v1/testnet/nft/collections/{id}A Testnet NFT collection - GET
/v1/testnet/nft/collections/{id}/nftsThe live NFTs of a Testnet collection - GET
/v1/testnet/nft/historyTestnet NFT events, newest first - GET
/v1/testnet/nft/{id}A Testnet NFT with the offers standing on it - GET
/v1/testnet/nft/{id}/offersThe offers standing on a Testnet NFT, split by side - GET
/v1/testnet/{address}Live Testnet XRP balance, reserve, sequence and settings of an account, straight from the network - POST
/v1/testnet/rpcThe XRP Ledger's own READ commands against our Testnet node — the half of Testnet that is not in the index: account_objects, book_offers, amm_info, ledger_entry, server_info and the rest. Reads only (submitting is POST /testnet/submit); the node's in-band error (actNotFound, entryNotFound) rides in result with a 200, as on Mainnet - POST
/v1/testnet/submitSubmit a SIGNED transaction to Testnet through our own node — the contract of POST /submit with the prefix changed. Nothing here signs or holds a seed; fund an account with POST /faucet first - GET
/v1/testnet/tx/{hash}A Testnet transaction and its final result, from our node: validated, the ledger it closed in, result (meta.TransactionResult), the transaction and its meta. 404 until the node has seen it