⚡ Heavy Workload? We Offer Higher Rate Limits to Accelerate Your dApp Performance
Method: POST ripple_path_find
The ripple_path_find method is a simplified version of the path_find method that provides a single response with a payment path you can use right away.
It is available in both the WebSocket and JSON-RPC APIs.
However, the results tend to become outdated as time passes.
Instead of making multiple calls to stay updated, you should instead use the path_find method to subscribe to continued updates where possible.
source_account - String
Unique address of the account that would send funds in a transaction
destination_account - String
Unique address of the account that would receive funds in a transaction
destination_amount - String or Object
Currency Amount that the destination account would receive in a transaction.
This requests a path to deliver as much as possible, while spending no more than the amount specified in send_max (if provided).
send_max - String or Object
(Optional) Currency Amount that would be spent in the transaction. Cannot be used with source_currencies.
source_currencies - Array
(Optional) Array of currencies that the source account might want to spend.
Each entry in the array should be a JSON object with a mandatory currency field and optional issuer field, like how currency amounts are specified. Cannot contain more than 18 source currencies.
By default, uses all source currencies available up to a maximum of 88 different currency/issuer pairs.
None - None
ledger_hash - String
(Optional) A 20-byte hex string for the ledger version to use.
ledger_index - String or Unsigned Integer
(Optional) The ledger index of the ledger to use, or a shortcut string to choose a ledger automatically.