Skip to main content
Set the following options:
  • allowSwitchChain: false to prevent automatic chain switching
  • allowDestinationCall: true to allow the bridge to complete the swap on the destination chain
Yes. LI.FI emits on-chain events for all transfers and includes the integrator parameter. You can filter by this parameter to identify swaps from your client.
No. The /quote/contractCalls endpoint does not support sending native ETH.
Yes. The quote includes an estimated gas amount and transaction data.
Add ?skipSimulation=true to the request. This skips on-chain simulation and improves response time.
Include the fromAmountGas parameter in your request. This is required for gaszip to function.
  • On EVM: A balance check is required to generate transaction data.
  • On Bitcoin and Sui: A balance check is also performed during transaction generation.
If order is not set, the default is CHEAPEST.
Use the LI.FI status endpoint. It reports full or partial completion, the token and amount delivered, and the destination chain.
Timing is configurable per request. Use a short target for fast flow, or wait longer on larger trades to collect more provider responses. A common pattern is ~400ms minimum for fast traders and ~1s with at least four results for larger trades.
Yes. LI.FI aggregates multiple providers, including Relay and Jupiter, giving unified fee collection, tracking, and routing without duplicate integrations.
Use the quote endpoint when you want the best single option with ready-to-execute transaction data. Use the routes endpoint when you need to present multiple choices before fetching step data. You can also filter to simpler, single-transaction flows for mainstream UX.
Yes. LI.FI can fund on one chain and complete an NFT purchase on another by passing call data; some marketplaces may need allowlisting or extra integration steps.