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.
Network Support
Request format.
XRPL’s HTTP API is JSON-RPC shaped but not JSON-RPC 2.0: the body is{"method": "...", "params": [{...}]}with nojsonrpcoridfield.
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 a200 OKresponse as"status": "error"with anerrortoken (for examplelgrNotFound,actNotFound), anerror_codeand anerror_message. Checkresult.statusrather than the HTTP status.
Not served.sign,sign_forandchannel_authorizetake a secret key and are refused withunknownCmd; sign transactions client-side and send them withsubmit.path_findand thepeer_status,consensusandserverstreams 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:ledger, transactions and validations streams and for subscribe.
Example request over WebSocket:
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.