This is the second step when bridging tokens. After computing a route with Compute Route (POST /v2/fungible/route), pass the route details and your addresses to this endpoint. It returns signable transaction messages that you can broadcast to the source chain.
The typical flow is: Compute Route → Generate Transaction → sign and broadcast → Track Transaction.
Input amount in smallest denomination.
Expected output amount from the route response.
Source chain ID.
Source asset denomination.
Destination chain ID.
Destination asset denomination.
Array of recipient and/or sender address for each chain in the path, corresponding to the required_chain_addresses array returned from a route request.
2Route operations from the /v2/fungible/route response.
Slippage tolerance as a percentage (e.g. "1" for 1%).
Signed OP hook data, required when the route has required_op_hook true.
Include blacklisted networks.
Successful response
Array of transaction objects. Each can be a cosmos_tx, evm_tx, or svm_tx.