XRPL Node
Read ledgers and transactions, and submit signed transactions — any transaction type the ledger has.
Transaction types you can submit (62)
POST /v1/submit relays any of these — you sign, it submits. Pick a type for its example JSON: the transaction as you would build it before signing. The list is the api's own (GET /v1/submit/types).
{ "TransactionType": "Payment", "Account": "rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn", "Destination": "ra5nK24KXen9AHvsdFTKHSANinZseWnPcX", "DeliverMax": { "currency": "USD", "value": "1", "issuer": "rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn" }, "Fee": "12", "Flags": 2147483648, "Sequence": 2 }
Ledger
Submit
- POST
/v1/submitSubmit signed transaction - POST
/v1/submit/previewDry-run transaction preview (400 on invalid tx input); sender_after = simulated sender position {balance, reserve, spendable}, null when no sender AccountRoot change - POST
/v1/rpcThe 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 - GET
/v1/submit/typesEvery transaction type POST /submit relays, each with an example: examples[type] = { json (the reference example, unsigned), txid (a real Mainnet transaction of that type, when the reference names one), summary } - GET
/v1/submit/feeCurrent network fees - GET
/v1/submit/account/{address}/sequenceAccount sequence number - GET
/v1/submit/account/{address}/inbound-tagsDestination-tag usage of recent inbound payments (send-screening advisory; tagsExpected = recent deposits overwhelmingly tagged) - GET
/v1/submit/tx/{hash}Lookup a submitted XRPL transaction by hash - GET
/v1/submit/ledger-entry/check/{checkId}Lookup a Check ledger entry by id