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 amounts of each 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
approvalDataparam in the quote has all the data to pass as query params to the check-allowance endpoint.
approvalDatafetched from the quote is to be used to make a smart contract method call on the frontend to give Socket contracts approval to spend user tokens on behalf of user.
build-txendpoint can be called to generate the transaction data to get approval from the user.
callDatafor the route needs to be fetched from the
/server/build-txendpoint. This is followed by a smart contract method call on the frontend, which is explained in the page below.