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

# Li.Fi

> Connect your Li.Fi account to Portal and start bridging & swapping across chains.

## Overview

Portal integrates with [Li.Fi](https://portal.li.fi/signup?referrer=portal) so you can bridge and swap tokens across multiple chains through Portal APIs and SDKs. This page covers the one‑time setup in Li.Fi and the Portal Dashboard.

## Steps to enable the Portal Li.Fi integration

### 1. Sign up for Li.Fi

* Create or access your Li.Fi account [here](https://portal.li.fi/signup?referrer=portal).
* Generate a Li.Fi API key in your Li.Fi dashboard.

<Note>Keep your API keys secure. You'll paste it into Portal in the next step.</Note>

### 2. Enable the Li.Fi integration in Portal

1. Open the [Portal Dashboard](https://app.portalhq.io).
2. Navigate to the `Integrations` page.
3. Locate the `Li.Fi` integration and add it.
4. Paste your Li.Fi API key for your selected Portal environment and save.

Once saved, Portal will proxy your SDK/API calls to Li.Fi using this key securely from Portal's servers, so you won't need to embed it in your application code.

<Note>Integrations are environment‑scoped. Repeat these steps per Portal environment.</Note>

## Gas-sponsored Solana swaps

Some Solana routes create an intermediate token account partway through the swap (for example a WSOL account for a route that hops through a SOL pool). That account creation is funded by the sending wallet, so a gas-sponsored wallet holding 0 SOL would otherwise fail on the rent for it.

Li.Fi exposes an `svmSponsor` field on the quote and routes requests: the account it names is used as the fee payer **and** the funder for any account creation in the route, so your sponsor covers that rent. When your Portal environment has a Solana gas sponsor enabled, Portal fills `svmSponsor` for you on Solana source routes, so no change is needed in your app.

To use a different account, pass `svmSponsor` (a valid Solana address) on the request and Portal will use it instead. Invalid values are ignored and fall back to the environment gas sponsor. On `/lifi/quote` it is a top-level field (`svmSponsor`); on `/lifi/routes` it goes inside `options` (`options.svmSponsor`).

<Note>`svmSponsor` is Solana (SVM) only and applies when the source chain is Solana. It is available on `/lifi/quote` and `/lifi/routes`; routes bake it into the returned steps, so `/lifi/route-step-details` inherits it.</Note>

## Next steps

Implement the flow in your app using our SDK guides for Li.Fi:

* [Bridge & Swap with Li.Fi](/apis/enclave-mpc/guide/lifi) using the Enclave MPC API
* [Bridge & Swap with Li.Fi](/sdks/ios/guide/lifi) using the iOS SDK
* [Bridge & Swap with Li.Fi](/sdks/android/guide/lifi) using the Android SDK
* [Bridge & Swap with Li.Fi](/sdks/web/guide/lifi) using the Web SDK
* [Bridge & Swap with Li.Fi](/sdks/react-native/guide/lifi) using the React Native SDK
* [Bridge & Swap with Li.Fi](/sdks/flutter/guide/lifi) using the Flutter SDK