Skip to main content
toAmount is the estimated post-swap amount. toAmountMin is the quoted minimum output amount, reflecting applicable slippage and any known transfer-tax adjustments applied to the quote.A lower toAmount can result from price impact or market fluctuations.For fee-on-transfer tokens below the configured tax limit, LI.FI may already adjust both toAmount and toAmountMin for the known buy/sell tax in addition to slippage. Use the returned toAmountMin rather than recomputing it from the slippage parameter. The adjustment depends on the available tax data and does not cover dynamic or undetected taxes. Where tax screening applies, tokens with a detected buy or sell tax at or above the configured limit are rejected by that check — see Token support.To filter out routes with high price impact, use the maxPriceImpact parameter.
  • Slippage: Difference between toAmount and toAmountMin
  • Price impact: Difference between the original quote and toAmount
When no dynamic or tool-specific default applies, LI.FI commonly uses 0.5% per step (0.005 on the API). With Smart Slippage, integrators may receive a data-driven server-side default instead. Slippage is expressed as a decimal from 0 to 1, where 1 = 100%.For example, a route that includes swap + bridge + swap can result in 1.5% total slippage in that sense, but there are some exceptions:
  • Some exchanges, such as those on Solana, may suggest their own slippage if none is set.
  • Some bridges, such as cBridge for small amounts, may enforce their own slippage to help ensure successful transaction execution. In those cases, we pass on that slippage.
The API accepts manually set slippage of up to 1 or 100%, expressed as a decimal.We recommend not tracking the slippage set by the user directly, but instead tracking the toAmountMin from our quotes. This is the value we promise the user after slippage. If they receive less than this amount, something is likely off. We also track this on our side so we can investigate transactions that users report.To apply one slippage budget to the whole route instead of to each step, see the next question.
Yes. Send slippageScope=route with your slippage, and the value becomes the budget for the whole route instead of the tolerance for each step. LI.FI returns one floor, toAmountMin = ceil(expected output × (1 − slippage)), and builds the transaction to deliver at least that amount. If it can’t, the transaction reverts, or the transfer is reported as not fulfilled on /v1/status.At slippage=0.01, on a swap followed by a bridge that prices its own output, each step can use up to 1% with per-step slippage, while the route as a whole uses at most 1% with route-wide slippage.It covers EVM routes with at most one swap, and refuses the rest instead of falling back to per-step slippage. See Route-wide Slippage for supported routes, the response fields and error handling.
No. Increasing slippage tolerance does not prevent rate changes. It only widens the acceptable range before failing the transaction.
There is no universal value. A 0.5% tolerance is a common starting point, but the appropriate value depends on the token, chain, trade size and route. Omitting the parameter allows LI.FI to select, where data coverage permits, a data-driven server-side default.
It depends on the token, chain, and amount. There is no universal value.To reduce failures:
  • Execute the quote immediately
  • For Solana same-chain swaps, omit the slippage parameter to let LI.FI auto-calculate
LI.FI calculates price impact using the difference in USD value between input and output tokens.Price impact filtering does not apply to trades under $10.
  • Execute the quote immediately
  • Refresh the quote if delayed
  • Increase the allowed slippage in your API request
Yes. A minimum received amount is enforced when the user signs; execution must deliver at least that minimum or it reverts. Slippage exists because prices/liquidity move between quote and execution. Auto slippage can select a buffer based on asset liquidity (lower for stablecoins, higher for long-tail assets). Where no dynamic or tool-specific default applies, LI.FI commonly uses ~0.5%, with the minimum slightly below the estimate to absorb normal movement.
Yes. Smart Slippage is available to all integrators. LI.FI can apply a server-side default before route generation and separately returns advisory recommendedSlippage values on generated route steps. These values may differ because step enrichment can inspect actual intermediate tokens while the earlier default cannot.See Smart Slippage for the field’s states, how recommendations are derived, chain and token coverage, and how it interacts with the SDK and Widget slippage config. No enterprise enablement is required; recommendations depend on current data coverage.