POST
/v1/rpc
The XRP Ledger's own READ commands against MAINNET — the twin of POST /testnet/rpc, so a developer who learned the sandbox changes the prefix and nothing else. Reads only (submitting is POST /submit); the node's in-band error (actNotFound, entryNotFound) rides in result with a 200, as on the node
AuthNone — works without a key
Request
POST
https://api.xrpl.to/v1/rpcBody
Body fieldsas documented
{ method (one of the read commands), params (the command's own fields as an object) }
curl -X POST 'https://api.xrpl.to/v1/rpc'
No public sample for this one — copy the code and fill in your own values.
Response
No public sample for this endpoint — run the code on the right with your own values to see the response.
Shapeas documented
{ success, took, method, result (the node's own result, verbatim) }
What it does
The XRP Ledger's own READ commands against MAINNET — the twin of POST /testnet/rpc, so a developer who learned the sandbox changes the prefix and nothing else. Reads only (submitting is POST /submit); the node's in-band error (actNotFound, entryNotFound) rides in result with a 200, as on the node
- Notes
- Same list as /testnet/rpc: account_channels, account_currencies, account_info, account_lines, account_nfts, account_objects, account_offers, account_tx, amm_info, book_changes, book_offers, channel_verify, deposit_authorized, feature, fee, gateway_balances, get_aggregate_price, ledger, ledger_closed, ledger_current, ledger_data, ledger_entry, ledger_header, ledger_index, manifest, mpt_holders, nft_buy_offers, nft_history, nft_info, nft_sell_offers, nfts_by_issuer, noripple_check, owner_info, ping, random, ripple_path_find, server_definitions, server_info, server_state, simulate, transaction_entry, tx, tx_history, tx_reduce_relay, vault_info, version. subscribe, unsubscribe and path_find need a session — use the WebSocket
Transaction hashes are 64-character hex. Submit relays whatever you signed: the type list below is what the ledger accepts today. Every transaction type you can submit →