Get All Possible Routes
Get all possible routes for swapping X to Y
Last updated
Was this helpful?
Get all possible routes for swapping X to Y
Last updated
Was this helpful?
It goes through all the possible to find a list of best possible routes for swapping X to Y.
from * Asset
Example: {"blockchain": "BSC", "symbol": "BNB", "address": null}
to * Asset
Example: {"blockchain": "AVAX_CCHAIN", "symbol": "USDT.E", "address": "0xc7198437980c041c805a1edcba50c1ce5db95118"}
amount * String
Description: The human-readable amount of asset from that is going to be swapped.
Example: 0.28
connectedWallets
Description: Optional list of all connected wallets of user in all blockchains.
slippage number
Description: Amount of user's preferred slippage in percent. if you don't send it, it will assume 0.5% slippage. (It's used to filter the swappers or routes that are not suitable for the given slippage)
contractCall Boolean
Description: set this parameter to true if you want to send transactions through a contract. It will filter swappers that are not possible to be called by another contract.
Caution: if you call Rango contracts using your contract and your contract is not white listed in some underlying protocols like Thorchain, user fund may stuck forever in Thorchain contracts. In this case, you need to exclude these swappers using this flag or ask related protocols to white list your contract.
Example: true
affiliateRef String
Example: K3ldk3
affiliatePercent String
Description: The dApp transaction fee in percent. Rango allows affiliate percent up to maximum of 3.0 percent.
Example: 1.5 which means 1.5 percent of the input amount
affiliateWallets
Description: List of affiliate wallets per blockchain for referral rewards. If this parameter is not provided, the wallet used for generating the affiliateRef will be used. By passing this parameter, you can override the wallet address used for the dApp transaction fee for each blockchain.
disableMultiStepTx Boolean
Description: Some bridges requires more than one transaction for each swap. For example, some bridges require transaction on both source and destination blockchains by the users. Using this flag, you could enable routing via these protocols. Default is true.
Note: At the moment, only Voyager bridge subjects to this condition.
Default: true
blockchains String
Description: Pass comma separated list of blockchains if you want to filter meta blockchains to some specific ones.
Example: POLYGON,ETH
blockchainsExclude Boolean
Description: A boolean value indicating whether the specified blockchains should be excluded or included in the response.
Example: true
swappers String
Description: Pass comma separated list of swappers if you want to filter meta swappers to some specific ones.
Example: Across,OneInchEth
swappersExclude Boolean
Description: A boolean value indicating whether the specified swappers should be excluded or included in the response.
Example: false
swappersGroups String
Description: Pass comma separated list of swapper groups if you want to filter meta swapper groups to some specific ones.
Example: Across,1Inch
swappersGroupsExclude Boolean
Description: A boolean value indicating whether the specified swapper groups should be excluded or included in the response.
Example: false
transactionTypes String
Description: Pass comma separated list of transaction types if you want to filter blockchains types to some specific ones.
Example: EVM,COSMOS
transactionTypesExclude Boolean
Description: A boolean value indicating whether the specified transaction types should be excluded or included in the response.
Example: false
enableCentralizedSwappers Boolean
Description: Set this flag to true if you want to enable routing through the centralized solutions and obtain the associated metadata, including related swappers and tokens. The default value for this argument is false.
Caution: To enable these swappers, you must pass the user's IP to the Rango API for compliance checks. Additionally, user funds may be held for KYC if their wallet is flagged as risky by the screening solutions implemented by these protocols.
Default: false
avoidNativeFeeBoolean
Description: When this condition is true, swappers that charge fees in native tokens will be excluded. For instance, when called from an AA account. Swappers like Stargate charge user fees in native tokens instead of the input amount, causing the transaction value to differ from the user's input amount. Alternatively, the user may need to transfer native tokens in a contract call to cover these protocol fees. Although you can disable these protocols using this flag, we do not recommend it as it reduces the coverage of routes.
Default: false
interChainMessage
Description: Info about inter-chain message (Source & Destination contracts and IM Message) for cross-chain messaging.
messagingProtocols
Description: List of messaging protocols to be used for passing interchain messages.
routeId
The unique request Id which is generated for this request by the server.
Example: d10657ce-b13a-405c-825b-b47f8a5016ad
requestAmount
Description: The human readable input amount from the request.
from
Description: The source asset.
to
Description: The destination asset.
results
Description: list of of all possible routes.
diagnosisMessages
Description: A list of string messages that might be the cause of not finding the route. It's just for display purposes.
missingBlockchains
Description: List of all blockchains which are necessary to be present for the best route and the user has not provided any connected wallets for it. A null or empty list indicates that there is no problem.
blockchains
Description: List of all accepted blockchains, an empty list means no filter is required.
processingLimitReached
Description: A warning indicates that it took too much time to find the best route and the server could not find any routes from X to Y.
walletNotSupportingFromBlockchain
Description: A warning indicating that none of your wallets have the same blockchain as X asset.
error
Description: Error occurred during the operation.
errorCode
Description: Error code shows the type of error.
traceId
Description: Trace Id helps Rango support team to trace an issue.
When user confirms one of the routes and you want to go to the next step (creating transaction), it's required to call the with the relevant route request Id. Otherwise, Rango won't create the transaction for you.
Description: The source
Description: The destination
Description: The . In the Rango Exchange App, an affiliate key is generated using a wallet address, and this same wallet address is used to receive the fee charged by the dApp for the request.