> ## Documentation Index
> Fetch the complete documentation index at: https://docs.li.fi/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration

<Accordion title="How can I ensure users only sign on the source chain while allowing the bridge to complete the swap on the destination chain?">
  Set the following options:

  * <code>allowSwitchChain: false</code> to prevent automatic chain switching
  * <code>allowDestinationCall: true</code> to allow the bridge to complete the swap on the destination chain
</Accordion>

<Accordion title="Can I detect on-chain if a swap was made via a specific client using the LI.FI widget?">
  Yes. LI.FI emits on-chain events for all transfers and includes the <code>integrator</code> parameter.
  You can filter by this parameter to identify swaps from your client.
</Accordion>

<Accordion title="Can I send native ETH with a payable function via the /quote/contractCalls endpoint?">
  No. The <code>/quote/contractCalls</code> endpoint does not support sending native ETH.
</Accordion>

<Accordion title="Does the quote response include gas information?">
  Yes. The quote includes an estimated gas amount and transaction data.
</Accordion>

<Accordion title="How can we improve the response speed of /advanced/stepTransaction calls?">
  Add <code>?skipSimulation=true</code> to the request. This skips on-chain simulation and improves response time.
</Accordion>

<Accordion title="How do I ensure the gaszip service works?">
  Include the <code>fromAmountGas</code> parameter in your request. This is required for gaszip to function.
</Accordion>

<Accordion title="When does LI.FI require a balance check during transaction generation?">
  * On EVM: A balance check is required to generate transaction data.
  * On Bitcoin and Sui: A balance check is also performed during transaction generation.
</Accordion>

<Accordion title="What is the default sorting behavior if the order parameter is not provided?">
  If <code>order</code> is not set, the default is <code>CHEAPEST</code>.
</Accordion>

<Accordion title="How can we track cross-chain transaction status?">
  Use the LI.FI status endpoint. It reports full or partial completion, the token and amount delivered, and the destination chain.
</Accordion>

<Accordion title="How can we tune quote speed versus quote quality?">
  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.
</Accordion>

<Accordion title="Does LI.FI already aggregate providers like Relay and Jupiter?">
  Yes. LI.FI aggregates multiple providers, including Relay and Jupiter, giving unified fee collection, tracking, and routing without duplicate integrations.
</Accordion>

<Accordion title="When should we use the quote endpoint versus the routes endpoint, and can we force single-transaction flows?">
  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.
</Accordion>

<Accordion title="Does LI.FI support cross-chain NFT purchases?">
  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.
</Accordion>