from-token-list, representing tokens that can be sent from the sending chain and
to-token-list,representing tokens that can be received on the destination chain. These two lists need to be separately shown to a user.
quoteendpoint with amount of sending token. These routes need to be shown to the user. These routes also consider any swaps involved.
userTxTypecan be used to infer the type of transaction. This data can be used to break down and display components of the route on the UI.
fund-movrand it encompasses the dex swap and bridging transaction metadata in the steps array nested in the route. In some routes such as the one involving the Polygon Native bridge, the dex swap needs to be performed first by the user and then bridged as the Polygon Native bridge requires only wallet users to burn the token. In such cases, a separate transaction with type
/route/build-next-txcan be called which will return the transaction data of the first tx.
/route/prepareendpoint needs to be called with the userTxIndex, activeRouteId [Returned in
/route/start] & transaction hash [Hash of transaction user performed]
/route/prepareneeds to be called periodically to check if the next transaction can be initiated. Then,
route/build-next-txcan be called again which will return the transaction data for the next transaction.
route/build-next-txreturns the transaction data for the next tx. However, as mentioned earlier, it cannot be executed until the
/route/prepareendpoint returns ready status.
/route/preparereturns completed status, there is not further transaction to be executed and the route can be marked as fully done.