Compute Route
This is the first step when bridging tokens between chains. Call this endpoint with your source and destination assets to find the optimal transfer route. The response includes the expected output amount, USD value estimates, and an ordered list of operations.
After receiving a route, pass the full response (including operations) to the Generate Transaction endpoint (POST /v2/fungible/msgs) to get signable transaction messages you can broadcast.
If the route involves an IBC transfer between the Initia L1 chain and an external Cosmos chain, the endpoint also checks that the transfer fits within the current IBC rate-limit capacity. When the requested amount exceeds the remaining send or receive capacity, the request is rejected with a 400 error whose info field reports the remaining capacity in human-readable units.
If the only candidate route for an EVM source uses CCTP and targets an L2 destination directly, the request is rejected with a 400 error whose info field advises transferring to L1 first. When several candidate routes are considered and all of them fail, the endpoint returns the first captured route-processing error so the response describes the most relevant failure.
Body
Amount to send in the smallest denomination (e.g. "1000000" for 1 INIT).
Source chain ID.
Source asset denomination.
Destination chain ID.
Destination asset denomination.
Allow routes that may have higher risk.
Use Go Fast bridging. Automatically determined if not set.
Force an Optimistic withdrawal route.
Response
Successful response
Input amount.
Expected output amount.
Source chain ID.
Source asset denom.
Destination chain ID.
Destination asset denom.
Ordered list of transfer operations to execute.
All chain IDs that require an address, in order of usage by operations in the route. Use this to populate the address_list parameter in the Generate Transaction request.
Ordered list of all chain IDs involved in the route.
Whether the route involves a token swap.
Estimated output amount before fees and slippage adjustments.
Estimated fees for the route. Each entry describes a fee with its amount, behavior, and the originating asset.
Estimated time in seconds for the route to complete.
Number of transactions required to execute the route.
DEX venues used for swaps in the route, if any.
Primary DEX venue used for the route's swap.
Estimated price impact percentage for the swap.
USD value of the input amount.
USD value of the output amount.
Price impact warning (present when impact exceeds 5%).
Additional warning messages for the route, such as withdrawal duration notices.
Whether an OP hook is required for this route.