Get started
XRPL.to API
v1.20REST and WebSocket access to XRP Ledger tokens, market data, DEX trades, accounts and NFTs — the same API that powers xrpl.to.
Base URL
Rate Limits
Free key: 10 req/sec and 1M credits a month. Paid plans go up to 500 req/sec.
API Reference
All 332 endpoints, each with a sample request.
Attribution is required
If your app, site or bot shows xrpl.to data, show a visible clickable credit — Data by xrpl.to — on the same screen. It applies with no key, on Free and on every paid plan, and it is what keeps the API free. Serving our data again from your own API or dataset needs permission first. Building an indexer or aggregator? The Partner tier is free for integrations that credit us.Quick start
Top 10 tokens by 24h volume:
Top 10 NFT collections by 24h volume:
Requests with generic programmatic User-Agent strings (e.g. Python-urllib) may be challenged by the CDN/WAF with a non-JSON 403 before reaching the API. Always send a descriptive User-Agent identifying your app (e.g. "myapp/1.0").
Where to look
The reference follows the site: find it in a list, open one item, then sign and submit. Open the page for what you already have.
Submit relays whatever you signed — 62 transaction types today: every one is listed, with a Testnet sandbox link where the simulation has performed it, under XRPL Node → Transaction types.
Building with an AI coding agent
Point your agent at these rather than this page: the same reference, in a form it reads directly.
| Source | What it is |
|---|---|
| MCP server | POST https://api.xrpl.to/v1/mcp — read-only tools for tokens, NFTs, accounts and markets |
| llms.txt | What to call for what you have, the trade cycle, and the rules agents most often get wrong |
| OpenAPI 3.1 | Every HTTP endpoint and its parameters |
| /v1/docs | The JSON this page is built from, rate limits included |
| Copy for LLM | On each section of this page: that section as markdown |
Keep keys and seeds out of generated code
Never put an API key in browser or mobile code; call the API from a server. Sign transactions on the user’s device: the API never needs a seed, so an agent should never ask for one. Try things with the testnet faucet and dry-run with POST /v1/submit/preview before spending real XRP.