An address's core state
API · /xrpl-api
XRP Ledger (XRPL) API
Live on-chain data from the XRP Ledger (XRPL), the decentralized blockchain behind XRP, served straight from public XRPL nodes by JSON-RPC — no key, nothing cached. The account endpoint returns any address's core state: its XRP balance, transaction sequence, the number of objects it owns, and its account flags and domain — the genesis-era account rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh holds tens of thousands of XRP. The balances endpoint returns the full wallet: the XRP balance plus every issued-currency trustline (token or stablecoin) the account holds, with the issuer, currency and amount, decoding hex currency codes to readable tickers. The transactions endpoint returns the account's most recent ledger activity — payments, DEX offers, trustline changes — each with its hash, type, amount, fee, result and time. The server endpoint returns the state of the ledger itself: the latest validated ledger index and age, the base and per-object XRP reserves, the current fee and the node software version — the network health a wallet or explorer needs. Everything is read live from the XRPL, nothing stored. This is the XRP Ledger on-chain layer for any wallet, explorer, exchange, payments or analytics app. Distinct from EVM and Solana on-chain APIs and from price feeds — this is XRPL account state, token balances, transactions and ledger health. 4 endpoints, no key on our side.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 209 ms
- Server probes · 24h
- Subscribers
- 3,100
- active
- Total calls
- 25
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 4,000 calls / month
- 5 requests / second
- Hard cap (429 above quota, no overage)
- 4,000 calls/month
- 5 req/sec
- Account, balances, server
- No credit card
Starter
€13.00 /month
- 100,000 calls / month
- 12 requests / second
- Hard cap (429 above quota, no overage)
- 100,000 calls/month
- 12 req/sec
- Transactions + token trustlines
- Email support
Pro
€33.00 /month
- 600,000 calls / month
- 30 requests / second
- Hard cap (429 above quota, no overage)
- 600,000 calls/month
- 30 req/sec
- Wallet & explorer pipelines
- Priority support
Mega
€79.00 /month
- 3,500,000 calls / month
- 80 requests / second
- Hard cap (429 above quota, no overage)
- 3,500,000 calls/month
- 80 req/sec
- Exchange & analytics scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Rectifier Ripple API
Rectifier ripple and smoothing-capacitor maths as an API, computed locally and deterministically. The ripple endpoint computes the peak-to-peak ripple voltage left on a reservoir (smoothing) capacitor after a rectifier, Vr = I_load/(f_ripple·C), where the ripple frequency is the line frequency for a half-wave rectifier and twice it for a full-wave or bridge rectifier — and it solves for whichever of the load current, the capacitance or the ripple you leave out, also giving the RMS ripple. The capacitor endpoint sizes the smoothing capacitor for a target ripple, C = I_load/(f_ripple·Vr), and the energy it stores. The output endpoint gives the DC output of the rectifier from the transformer RMS voltage: the peak Vrms·√2, minus the diode drops in the conduction path (one for half-wave and centre-tapped, two for a bridge), the average DC voltage and, given the ripple, the ripple factor. Everything is computed locally and deterministically, so it is instant and private. Ideal for power-supply and electronics-design tools, linear PSU, charger and audio-amplifier design, and electronics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is rectifier ripple and filtering; for Ohm's law, reactance and RC time constants use an Ohm's-law API.
api.oanor.com/rectifier-api
Crypto Derivatives Exchanges API
Live ranking and directory of crypto derivatives venues — the platforms that run perpetual and futures markets — served from the public CoinGecko feed with no key and nothing cached. This is a venue-level view of the derivatives market, distinct from spot-exchange directories, per-contract open-interest feeds and single-exchange tickers: it ranks the derivatives platforms themselves. The exchanges endpoint returns the venues ranked by open interest (or by 24-hour volume), each with its open interest in BTC, 24-hour derivatives volume in BTC, the number of perpetual and futures pairs it lists, its country and the year it was established — so one call tells you who the biggest derivatives venues are and how concentrated open interest is. The exchange endpoint returns a single venue's full profile by id. The list endpoint returns every derivatives-exchange id and name for lookup and autocomplete. Everything is read live from CoinGecko on each request, nothing stored beyond a short protective cache. Ideal for derivatives dashboards, open-interest and market-structure analytics, venue comparison and trading tools. Live, no key. 3 endpoints. For per-contract funding and open-interest history use a derivatives or open-interest API.
api.oanor.com/derivativesexchanges-api
Crypto.com Exchange API
Live spot market data from the Crypto.com Exchange, one of the largest global retail crypto venues and the heart of the CRO ecosystem, served straight from its public API with no key and nothing cached. The ticker endpoint returns a market's last price, best bid and ask, the spread, 24-hour high and low, 24-hour change and base and quote volume. The tickers endpoint returns every spot market for a quote currency ranked by 24-hour quote volume, so one call gives you the most-traded pairs on the venue. The instruments endpoint lists the tradable spot pairs with their price and quantity tick sizes and decimal precision. The book endpoint returns live order-book depth — every bid and ask level with price, amount and order count, plus the best bid/ask and spread. Everything is read live from Crypto.com on each request, nothing stored; perpetual contracts are excluded so you get clean spot data. A distinct global venue, separate from the other exchange feeds on the marketplace. Ideal for trading bots, price tickers, arbitrage scanners, portfolio trackers and market dashboards. Live, no key. 4 spot endpoints. For perpetuals or candles use a derivatives or OHLC API.
api.oanor.com/cryptocom-api
Crypto Trending API
What the crypto market is searching for right now, served live from the public CoinGecko trending feed with no key. This is hype and attention data — distinct from market-cap rankings, exchange tickers and DeFi feeds — surfacing the coins, NFT collections and categories with the biggest spike in search interest over the last 24 hours. The coins endpoint returns the trending coins ranked by search popularity, each with its live USD price, 24-hour change, market cap, 24-hour volume, market-cap rank and BTC price. The nfts endpoint returns the trending NFT collections with floor price (native and display), 24-hour floor change and 24-hour volume. The categories endpoint returns the trending narratives and sectors with market cap, volume and 24-hour change. Trending means ranked by CoinGecko search popularity, so rank 1 is the single most-searched asset of the moment — exactly the signal traders, bots and dashboards use to catch a move early. Read live from CoinGecko, nothing stored beyond a short protective cache. Ideal for crypto dashboards, trading bots, sentiment and hype trackers, and discovery feeds. Live, no key. 3 trending endpoints. For full price history use an OHLC or exchange API.
api.oanor.com/cryptotrending-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for XRP Ledger (XRPL) API?
What's the rate limit for XRP Ledger (XRPL) API?
How much does XRP Ledger (XRPL) API cost?
Can I cancel my subscription anytime?
Is XRP Ledger (XRPL) API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/xrpl-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/xrpl-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/xrpl-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/xrpl-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.