Skip to main content

Start building on XRPL for free

Create an endpoint in under a minute. The Free plan includes 50 million compute units a month, and no credit card is required.

Try free
The XRP Ledger (XRPL) is a decentralized Layer 1 blockchain built for payments, with native support for issued currencies, a built-in decentralized exchange, automated market makers and NFTs. Validation Cloud serves the complete public ledger history, from ledger 32,570 to the current ledger, with WebSocket and HTTPS access. Developer docs: https://xrpl.org/docs Mainnet block explorer: https://livenet.xrpl.org

Network Support

Request format.

XRPL’s HTTP API is JSON-RPC shaped but not JSON-RPC 2.0: the body is {"method": "...", "params": [{...}]} with no jsonrpc or id field.

Over WebSocket, send {"id": 1, "command": "...", ...} with the parameters at the top level, as the xrpl.js and xrpl-py libraries do.

The JSON-RPC shaped request {"jsonrpc": "2.0", "id": 1, "method": "...", "params": [{...}]} is accepted over WebSocket as well.
Validated by default. Responses come from Clio, which serves validated ledger data. Requests that need the open ledger (ledger_current, submit, fee, or any request with "ledger_index": "current") are forwarded to rippled automatically.
Errors are answers. XRPL reports failures inside a 200 OK response as "status": "error" with an error token (for example lgrNotFound, actNotFound), an error_code and an error_message. Check result.status rather than the HTTP status.
Not served. sign, sign_for and channel_authorize take a secret key and are refused with unknownCmd; sign transactions client-side and send them with submit. path_find and the peer_status, consensus and server streams are not available.
WebSocket clients MUST respond to server ping frames, otherwise the connection will be closed and re-established every minute.

Getting Started

To start building on XRPL, connect your application to an XRPL endpoint and send XRPL API requests. Example request over HTTPS:
Use WebSocket for the ledger, transactions and validations streams and for subscribe. Example request over WebSocket:
With xrpl.js:

Compute Units

Over WebSocket each method costs the same as over HTTPS.

Every message pushed on a subscription (ledgerClosed, transaction, validationReceived, manifestReceived, bookChanges) is billed as one notification at 10 Compute Units regardless of size.