getQuotes

The source chain from which the cross-chain swap will originate. Can be specified as chain ID or name. See here for the list of supported chains

The destination chain where tokens will be received after the cross-chain swap. Can be specified as chain ID or name. See here for the list of supported chains

The contract address of the token to sell on the origin chain. Format varies by chain type (EVM address for EVM/HyperCore chains, token mint address for Solana, base58check address for Tron)

The contract address of the token to buy on the destination chain. Format varies by chain type (EVM address for EVM/HyperCore chains, token mint address for Solana, base58check address for Tron)

The amount of sellToken (in sellToken's base units) to sell on the origin chain

The wallet address on the origin chain that holds the sellToken balance and will initiate the cross-chain transaction

The wallet address on the destination chain that will receive the buyToken. If not specified, defaults to originAddress on the destination chain

The Solana address that will pay for transaction fees when the origin chain is Solana. Only applicable for Solana origin chains

Pubkey of an integrator-held ephemeral keypair used as a one-shot extra transaction signer for Solana origin routes that require one (e.g. the CCTP event account). Generate a fresh keypair per request and sign the returned transaction with it; the account must not already exist on-chain and is not reusable afterwards. Routes requiring an ephemeral signer are only quoted when this is set. Only applicable for Solana origin chains

The maximum acceptable slippage for each swap or bridge step of the cross-chain swap in basis points (100 = 1%)

Comma-separated list of bridge providers to exclude from routing

Comma-separated list of bridge providers to include in routing. Mutually exclusive with excludedBridges

Comma-separated list of DEX sources to exclude from routing on both chains

The trading fee amounts in basis points to charge on the origin chain (supports single or comma-separated values). Must be used together with feeRecipient. When multiple values are provided, must match the length of feeRecipient. Note: integrator fee collection is not yet supported for Tron-originated routes.

The wallet addresses to receive trading fees on the origin chain (supports single or comma-separated values). Must be used together with feeBps. When multiple values are provided, must match the length of feeBps. Note: integrator fee collection is not yet supported for Tron-originated routes.

The token addresses for fee collection on the origin chain (supports single or comma-separated values). Must be the same as sellToken. When multiple values are provided, must match the length of feeBps. If omitted, defaults to sellToken. Some routes collect the integrator fee through the bridge provider instead of on-chain; the fee still goes to feeRecipient, but it comes out of the token entering the bridge, which is not sellToken when the route swaps before bridging. Read fees.integratorFee.token for the token actually charged. Note: integrator fee collection is not yet supported for Tron-originated routes.

How to sort the returned quotes - either by speed (fastest execution time) or price (best exchange rate)

The maximum number of cross-chain quotes to return, between 1 and 10. Each quote represents a different combination of bridges and DEXs

Visit dashboard.0x.org to get your API Key