toToken to the protocol’s token address and LI.FI handles swaps, bridging, and the final deposit.
Each recipe below is end-to-end: request a quote, approve tokens, sign the transaction, and confirm the deposit.
All examples use
GET /quote. The same toToken addresses work with POST /advanced/routes and the LI.FI SDK. See API Integration or SDK Integration for full integration guides.Same-Chain: USDC → Morpho Vault (Base)
Deposit 1 USDC into a Spark-curated Morpho USDC vault on Base.toToken for any address listed in the Supported Protocols reference. Everything else stays the same.
Same-Chain: USDC → Aave (Ethereum)
Deposit 1000 USDC into Aave V3 on Ethereum, receiving aUSDC in return.Same-Chain: USDe → sUSDe on Ethena (Ethereum)
Deposit USDe into Ethena’s staked USDe (sUSDe) for yield.Same-Chain: USDC → Euler eUSDC-2 (Ethereum)
Deposit USDC into Euler V2’s USDC lending vault on Ethereum, receiving eUSDC-2 in return.Same-Chain: USDC → syrupUSDC on Maple (Ethereum)
Deposit USDC into Maple Finance’s Syrup USDC pool on Ethereum, receiving syrupUSDC.Cross-Chain: ETH (Ethereum) → Morpho Vault (Base)
Deposit ETH from Ethereum into the Morpho vault on Base. LI.FI handles the bridge, intermediate swaps, and deposit.Cross-chain transfers require status polling via
GET /status. See Cross-Chain Composer Patterns for the full execution flow and partial failure handling.Cross-Chain: USDC (Ethereum) → Morpho Vault (Base)
Bridge USDC from Ethereum and deposit into the Spark-curated Morpho vault on Base. LI.FI handles the bridge and final deposit in one flow.Felix Vanilla Vaults
Felix Vanilla vaults are supported for deposit and withdraw.Same-Chain: Deposit into Felix Vanilla Vault
Neverland Vaults
Neverland vaults are supported for deposit and withdraw.Same-Chain: Deposit into Neverland Vault
Depositing on Behalf of Another Address
Some protocols (such as Aave withonBehalfOf) support depositing on behalf of a different wallet. To use this pattern, set toAddress to the recipient’s address:
TypeScript
Not all protocols support deposit-on-behalf. If the target protocol does not support it, the API will return an error or ignore the
toAddress distinction. Test with your target protocol before relying on this pattern.Pendle Yield Tokens
Pendle enables yield tokenisation. Composer supports deposit and withdraw.Same-Chain: Deposit into Pendle
Deposit-Only Protocols
The following protocols support deposit only (no withdraw via Composer):- Maple — Lending protocol
- Ethena — USDe to sUSDe, ENA to sENA conversions
- Kinetiq — Staking (see Staking Recipes)
GET /quote pattern with the protocol’s vault/staking token as toToken.
General Pattern
Every vault deposit recipe follows the same pattern:toToken must be a vault token address from a supported protocol. Everything else is identical to a standard LI.FI swap or bridge request.
Next Steps
Withdrawals
Withdraw from protocol positions via Composer
Cross-Chain Patterns
Bridge + deposit patterns, status polling, and partial failure handling
Supported Protocols
Full protocol list with example token addresses
API Integration
Step-by-step REST API integration walkthrough

