Insights

XRPL API Guide - Free Token, Price & DEX Data API

There are two ways to read the XRP Ledger: ask the ledger itself, through its own commands, or ask an index that has already read every ledger and kept prices, trades and history. xrpl.to’s API does both, in 339 endpoints, free to start and with no key.

Read from the API’s own documentation, 19 October 2026 · base URL https://api.xrpl.to/v1

Two ways to read the XRP Ledger

The ledger’s own commandsAn index (a data API)
AnswersWhat is true now: a balance, trust lines, open offers, one transactionWhat happened over time: prices, candles, trades, rankings, search
Examplesaccount_info, account_lines, book_offers, tx/tokens, /ohlc, /holders, /search
HistoryRecent ledgers on most servers; full history on a fewKept and indexed, so a year of candles is one request
WhereAny XRP Ledger server, or POST /v1/rpc on xrpl.tohttps://api.xrpl.to/v1
The ledger’s commands are documented on xrpl.org. Use them for the current state and for submitting; use the index for anything a chart, a list or a search needs.

A first request

The two tokens with the most trading in the last 24 hours. No key, no sign-up:

Request
curl "https://api.xrpl.to/v1/tokens?sort=vol24hxrp&order=desc&limit=2"
Response
{
  "success": true,
  "total": 20468,
  "tokens": [
    {
      "name": "RLUSD",
      "issuer": "rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De",
      "currency": "524C555344000000000000000000000000000000",
      "exch": 0.762471760532176,
      "usd": "0.99909343433692883896",
      "vol24hxrp": 3092792.208121,
      "holders": 67589,
      "md5": "0dd550278b74cb6690fdae351e8e0df3"
    },
    {
      "name": "USDC",
      "issuer": "rGm7WCVp9gb4jZHWTEtGUr4dd74z2XuWhE",
      "currency": "5553444300000000000000000000000000000000",
      "exch": 0.7625438462711606,
      "usd": "0.9991878908037212248",
      "vol24hxrp": 312374.708854,
      "holders": 10399,
      "md5": "1c54f16ec1b45eef983f202b9954999b"
    }
  ]
}
A real response from 19 October 2026, trimmed to a few fields; the full token object has more. Quote the URL in a shell, or the&splits the command.

The ledger’s own commands, through the same API

POST /v1/rpc passes the XRP Ledger’s read commands to a full node and returns its answer unchanged, so one base URL covers both kinds of question. Here, the first account ever created on the ledger:

Request
curl -X POST "https://api.xrpl.to/v1/rpc" \
  -H "Content-Type: application/json" \
  -d '{"method":"account_info","params":{"account":"rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh","ledger_index":"validated"}}'
Response
{
  "success": true,
  "method": "account_info",
  "result": {
    "account_data": {
      "Account": "rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh",
      "Balance": "56785837001",
      "Sequence": 44196,
      "OwnerCount": 1
    },
    "ledger_index": 107755289,
    "validated": true
  }
}
Balance is in drops: one XRP is a million drops. Submitting a signed transaction is POST /v1/submit.

What it covers

NFTs, collections and marketplaces54
Accounts: balances, trust lines, history27
The XRP Ledger Testnet21
Charts and price history16
Market data13
Analytics10
Social mentions on X10
Submitting transactions9
Scam and phishing lists9
Trades, order books, pairs8
Tokens: lists, search, details7
Cross-chain bridge6
Ledgers and transactions5
Traders5
News4
Endpoints per area, counted from the API’s documentation. Every one has its own page with a live example in the API docs.

Live updates come over a WebSocket at wss://api.xrpl.to/ws/sync/; the WebSocket guide shows how to subscribe.

Limits and plans

Without a key: 2 req/sec burst, 30 req/min, 333/day (no key) + 0.25x endpoint windows, counted per IP address.

PlanPriceCredits a monthRequests a dayRequests a second
FreeFree1M33K10 (bursts of 20)
Developer$49 for 30 days · $490 a year10M400K50 (bursts of 100)
Business$499 for 30 days · $4,990 a year100M4M200 (bursts of 300)
Professional$999 for 30 days · $9,990 a year200M8M500 (bursts of 750)
Plans run for 30 days or a year and do not renew by themselves. Keys and plans are on the dashboard.

Four independent layers apply to every request; the strictest one wins. All 429 responses carry Retry-After plus X-RateLimit-Limit/-Remaining/-Reset headers and a JSON body with retryAfter.

The one condition: credit xrpl.to

Any app, website, bot, or dashboard that displays xrpl.to data must show a visible, clickable credit to xrpl.to on the same screen as that data — not buried in an about page. The credit can read Data by xrpl.to, linked to https://xrpl.to.

Storing our data and re-serving it from your own API, dataset, or public dashboard requires written permission first. Email hello@xrpl.to — the answer is usually yes, we just need to know who is doing it.

Questions

Is there a free XRP Ledger API?
Yes. The XRP Ledger’s own public servers answer its commands for free, and xrpl.to’s API serves prices, trades, pools, NFTs and holders free to start, with no key: 2 req/sec burst, 30 req/min, 333/day (no key) + 0.25x endpoint windows. A free key raises the limits.
Is there an alternative to Ripple’s Data API?
Yes. xrpl.to’s API serves what most people used Ripple’s Data API v2 for: token prices and candles, trades, account history and exchange rates, plus pools, NFTs and holder rankings.
Do I need an API key?
Not to start. Without a key: 2 req/sec burst, 30 req/min, 333/day (no key) + 0.25x endpoint windows. A free key gives 10 requests a second and 1M credits a month.

Guides to each part

Token data · Token search · Price history (OHLC) · DEX · Swap quotes · AMM pools · NFTs · WebSocket · How payments find a path