Mainnet
Mainnet REST API
https://ripple-mainnet.gateway.tatum.io
Free Ripple RPC (XRP)
Discover Ripple, a blockchain optimized for cross-border payments. Build secure and fast financial applications using its RPC gateway.
99.9%
2
24/7
FREE
Gateway
Connect to Ripple
Access reliable, enterprise-grade endpoints that power your dApp with ultra-low latency and 99.9% uptime.
Connect to Ripple Gateway
Make your first RPC call on Ripple's Blockchain Gateway.
Testnet
Testnet REST API
https://ripple-testnet.gateway.tatum.io
* Rate limit enabled - perfect for testing and development. For production, we recommend to Upgrade.
Ready for production?
Get 200 requests/second, priority support and advanced blockchain features.
Global Load Balancer
Route to nearest node
Batch RPC Calls
Multiple requests at once
Archive Nodes
Historical blockchain data
Debug & Trace
Advanced debugging
Advanced Analytics
Usage & performance
Bring Your Own RPC
Custom RPC gateways
Get Free API Key
Increase your limit and access all network features in Tatum Development Platform.
Accessible to Everyone
No signup. No paywalls. Just RPC that works. Great ideas come from everywhere.
Our Mission
With love by Tatum
Method reference
Ripple methods
Every method the Ripple gateway accepts, grouped by interface. 36 in total, read live from the node rather than kept by hand.
Mainnet is the live Ripple network. Every transaction it
accepts is final, and every XRP balance it
reports is real money.
Testnet answers the same methods on a network funded with tokens that have no market value. Develop there, then change the URL to Mainnet when the code is stable. Nothing else about your integration has to change.
Ripple answers over 2 interfaces: JSON-RPC and REST. Each is listed once below with every method it accepts. The endpoints differ per network, and all of them are in the gateway list above.
What sits between you and Ripple
A node is a machine running Ripple with a copy of the chain. Your code cannot ask the chain directly, it asks a node. The gateway picks a healthy one for every call, so you point at one URL instead of one machine.
Your application
FREE RPC gateway picks a healthy node
Node Node Node
- One URL, nothing to run or keep patched yourself.
- Calls routed to a node that is up and in sync.
- A failing node is skipped rather than returned to you as an error.
JSON-RPC
36 methods https://ripple-mainnet.gateway.tatum.io
The default. Every wallet, library and framework speaks it, and it is what you want unless you specifically need something else.
One POST carries a method name, its parameters and an id, and the response comes back on the same connection carrying that same id. Requests are independent, so there is no session to keep alive and nothing to reconnect, which is why it runs unchanged behind a load balancer or inside a serverless function. Send an array instead of a single object and the node works through the whole batch in one round trip.
Where it fits
- Anything your library already does for you. ethers, web3.js, viem and their equivalents all target this.
- Batching reads. One array of twenty calls costs one round trip instead of twenty.
- Stateless and serverless deployments, because nothing has to stay connected between calls.
- Historical queries, by passing a block number where you would otherwise pass latest.
Trade-offs
- It cannot push. Finding out that a block landed means polling for it, or moving to WebSocket.
- Wide log queries get refused. Page through in fixed block windows and merge the results yourself.
- Batch responses may come back in any order. Match them on id, never on position.
Enabled and tested methods
Read live from the endpoint, so this is what it actually serves today rather than what the protocol allows in principle. Anything not on this list returns a method-not-found error.
- account_channels
- Lists the payment channels an account has opened.
- account_currencies
- Lists the currencies an account can send or receive.
- account_info
- Returns an account: balance, sequence and settings.
- account_lines
- Lists the trust lines an account holds.
- account_nfts
- Lists the NFTs an account owns.
- account_objects
- Lists the ledger objects an account owns, such as offers and escrows.
- account_offers
- Lists the open order-book offers an account has placed.
- account_tx
- Returns the transaction history of an account.
- amm_info
- Returns the state of an automated market maker pool.
- book_offers
- Returns the open offers in an order book for a currency pair.
- channel_authorize
- Signs a claim authorising a payment channel withdrawal.
- channel_verify
- Verifies a payment channel claim signature.
- deposit_authorized
- Reports whether one account is authorised to send funds to another.
- fee
- Returns the current transaction cost and load-scaled fee levels.
- gateway_balances
- Returns the obligations a gateway account has issued.
- ledger
- Returns a ledger version, with optional transaction and state data.
- ledger_closed
- Returns the most recently closed ledger.
- ledger_current
- Returns the ledger version currently being built.
- ledger_data
- Returns the raw contents of a ledger, a page at a time.
- ledger_entry
- Returns a single object from the ledger state.
- manifest
- Returns the published manifest of a validator key.
- nft_buy_offers
- Lists the buy offers open against an NFT.
- nft_sell_offers
- Lists the sell offers open for an NFT.
- noripple_check
- Suggests fixes for trust-line settings that may block payments.
- ping
- Confirms the server is responding.
- random
- Returns a random number generated by the server.
- ripple_path_find
- Finds payment paths between two accounts, for interactive use.
- server_definitions
- Returns the protocol definitions the server understands.
- server_info
- Returns server state, version and load in human-readable form.
- server_state
- Returns server state in machine-readable form.
- submit
- Submits a signed transaction to the network.
- submit_multisigned
- Submits a transaction carrying several signatures.
- transaction_entry
- Returns a transaction from a specific ledger version.
- tx
- Returns a transaction by its hash, with the ledger it was validated in.
- tx_history
- Returns recent transactions across the network.
- version
- Returns the API versions the server supports.
Common JSON-RPC errors
What you are most likely to hit calling this interface, and what to do about it.
- -32700
- Parse error. The request body was not valid JSON. Check that the body is serialised JSON and that Content-Type is application/json.
- -32600
- Invalid request. The JSON parsed, but it is not a well-formed JSON-RPC call. Include jsonrpc, method and id fields. A batch must be a non-empty array.
- -32601
- Method not found. This node does not expose the method you called. Check the spelling and the namespace, and confirm the method is in the list above for this network. Tracing methods in particular are not enabled everywhere.
- -32602
- Invalid params. The method exists but the arguments are wrong. Check argument order and types. Most EVM methods want hex-encoded quantities, and a block parameter such as latest or a hex height.
- -32603
- Internal error. The node failed while handling an otherwise valid request. Retry with backoff. If it persists on one method, it is usually that method rather than the node.
- -32000
- Server error. A catch-all the node uses for execution failures, most often a reverted call or a request over a limit. Read the accompanying message. Execution reverted means your call failed on chain, not in transport. Narrow the block range if you are querying logs.
- HTTP 429
- Rate limited. You have exceeded the free tier request allowance. Back off and retry, batch reads into single calls, or move to a dedicated endpoint for production traffic.
- HTTP 413
- Payload too large. The request body exceeded what the node accepts. Split large batches into smaller ones.
REST
https://ripple-mainnet.gateway.tatum.io
Every resource has its own URL, so a request is just an address you can open.
Paste it into a browser, curl it, or bookmark it. There is no body to construct and no method name to look up, and because a read is a plain GET, ordinary HTTP caching applies at the CDN and in your own client. Responses are JSON, and the path itself usually tells you what you are getting.
Where it fits
- Getting oriented on an unfamiliar chain without writing any code first.
- Caching, because a GET can be cached by anything sitting between you and the node.
- Debugging, since the request that failed is a URL you can paste to a colleague.
Trade-offs
- You get exactly what the endpoint returns. There is no way to ask for less, or for more.
- Building a full picture takes several round trips where one batched JSON-RPC call would do.
- Paths carry version prefixes and shift between node releases more readily than method names do.
This endpoint does not publish a machine-readable method list, so there is nothing to enumerate here. Use server reflection against the endpoint above to see what it exposes.
Common REST errors
What you are most likely to hit calling this interface, and what to do about it.
- 400
- Bad request. A path or query parameter is malformed. Check the parameter format, and that path values are URL-encoded.
- 404
- Not found. Either the path is wrong, or the resource genuinely does not exist at that height. Confirm the path against the list above. A valid path can still 404 for pruned history on a non-archive node.
- 429
- Rate limited. You have exceeded the free tier request allowance. Back off and retry. REST responses cache well, so caching on your side removes most repeat traffic.
- 500
- Internal server error. The node failed while handling the request. Retry with backoff.
- 503
- Service unavailable. The node is starting, resyncing, or temporarily out of rotation. Retry with backoff; this is normally short-lived.
Blockchain Data
Indexed Ripple Data Insights
Complete on-chain data access, no infrastructure to run yourself. Query wallets, tokens, NFTs, and transaction history with lightning-fast APIs.
Blockchain Notifications
Real-time Ripple Alerts
Real-time webhooks for on-chain events. Stop polling the network - get instant alerts for transactions, smart contract events, and wallet activities.
Learn more
About Ripple
What it is, and guides for building on it.
The Ripple RPC documentation provides developers with the tools to interact programmatically with the Ripple blockchain, designed for fast, low-cost cross-border payments using its native cryptocurrency, XRP. The documentation includes API endpoints for querying blockchain data, managing transactions, and interacting with Ripple’s financial network. Developers can leverage Ripple’s efficient architecture and robust infrastructure to build decentralized financial applications, particularly in payment processing and remittance.
From the Tatum blog
%20(50).jpg)
Build on Ripple: How XRP Ledger Is Becoming the Layer for Real-World Asset To...
Explore how Ripple and the XRP Ledger are powering real-world asset tokenization in 2026. Learn how developers are bu...
What's new
Oct 8, 2026 Added
Notifications: Robinhood
Robinhood Chain is now live on Tatum’s Blockchain Notifications, with support for all notification types. Receive onc...
Oct 7, 2026 Added
RPC Gateway: WebSockets for Arbitrum and BSC
Stop polling. Start streaming. Tatum WebSocket subscriptions push blockchain updates to your app over a persistent co...
Sep 25, 2026 Deprecated
Harmony Networks Removal
Tatum is decommissioning its hosted Harmony Mainnet S0, Harmony Testnet S0, and Harmony Devnet S0 RPC services follow...
FAQ
Frequently Asked Questions
Everything you need to know about Ripple RPC endpoints
Quick Answer: What is Ripple RPC?
RPC (Remote Procedure Call) is the standard way to interact with the network programmatically - reading on-chain data, submitting transactions, and deploying smart contracts through JSON-RPC calls. The free tier ships 5 requests per minute with no registration required, which covers most learning and testing workflows. Production applications typically move to Tatum Premium for 200 requests per second and enterprise-grade reliability.
What is Ripple RPC?
RPC (Remote Procedure Call) is the interface that lets developers interact with the network: read on-chain data, submit transactions, and deploy smart contracts programmatically over standard JSON-RPC methods, without running your own node.
How do I connect to Ripple using these RPC endpoints?
Simply copy the RPC endpoint URL from above and configure it in your Web3 library (ethers.js, web3.js), wallet (MetaMask, Trust Wallet), or development tool (Hardhat, Truffle). The endpoint works immediately with no registration required for the free tier.
What are the rate limits for the free RPC tier?
Free tier RPC endpoints are limited to 5 requests per minute. This is perfect for testing and development. For production applications, we recommend upgrading to Tatum Premium which offers 200 requests per second with no daily limits.
Is Ripple RPC free forever?
Yes! Our free tier RPC endpoints are free forever with 5 requests per minute. This tier is perfect for learning, testing, and small projects. There are no hidden fees or time limits on the free tier.
What happens if I exceed the free tier rate limit?
If you exceed 5 requests per minute on the free tier, you'll receive an HTTP 429 (Too Many Requests) error. This is a standard rate limiting response. To avoid this, you can upgrade to Tatum Premium which offers 200 requests per second with no daily limits, perfect for production applications.
Can I use these Ripple RPC endpoints with MetaMask?
Yes! You can configure MetaMask to use our RPC endpoints. Simply copy the endpoint URL from above, go to MetaMask Settings > Networks > Add Network (or edit existing), and paste the RPC URL. This works with all EVM-compatible networks, including this one.
Are these RPC endpoints secure?
Yes, all our RPC endpoints use HTTPS encryption and follow enterprise-grade security practices. They're powered by Tatum's infrastructure which maintains 99.9% uptime.
What's the difference between mainnet and testnet RPC endpoints?
Mainnet carries real transactions with real value, so every write is final. Testnet runs on a separate network funded with free test tokens, which makes it the safe place to try new code, retry failed calls, and simulate edge cases. Always validate on testnet before pointing production traffic at mainnet.
How do I troubleshoot RPC connection errors?
If you're experiencing connection errors, check: 1) The RPC endpoint URL is correct, 2) You're not exceeding rate limits (5 req/min for free tier), 3) Your network allows HTTPS connections, 4) The network is currently operational. For persistent issues, check our status page or contact support.
Can I use these endpoints in production?
Free tier endpoints can be used in production for low-traffic applications (under 5 req/min). For production apps with higher traffic, we strongly recommend Tatum Premium for guaranteed uptime, faster rate limits, and enterprise SLA.
Related Blockchains
Explore Other Blockchains
Discover RPC endpoints for other popular blockchain networks
