Skip to main content
A withdrawal is a quote in the other direction: the user’s position token is fromToken and the token they want is toToken. Use GET /quote or POST /advanced/routes as for deposits. Only position tokens with an exit-position edge in Supported Protocols & Chains can be withdrawn through Composer.

How withdrawals work

The Composer route that redeems the position competes with other routes: if a DEX buys the position token for more, the quote sells it there instead. Check includedSteps for tool: "composer" to see which route you got. In a cross-chain withdrawal, Composer redeems the position on the source chain and the bridge carries the output to the destination chain, in one transaction.

Same-chain withdrawal

Withdraw 1 sparkUSDC (the Spark-curated Morpho USDC vault token, 18 decimals) into USDC on Base:
curl

Cross-chain withdrawal

Withdraw 1 sparkUSDC on Base and receive USDC on Arbitrum in one transaction. The quote’s includedSteps look like feeCollection, composer, polymerStandard.
curl
After the source-chain transaction confirms, poll GET /status; see Cross-chain deposits.

Execution flow

Withdrawals use the same allowance, transaction submission and status handling as deposits: approve the position token for the quote’s approvalAddress, send the transactionRequest, and poll status for cross-chain routes. See API Integration.

Protocols that support withdrawals

Filter the live Supported Protocols & Chains table by exit-position to see every position Composer can withdraw from, per chain. Protocols with only enter-position edges are deposit-only; users withdraw from them through the protocol’s own interface. IPOR vaults have exit edges but are not available through the LI.FI API.

Error handling

For other errors, see Error Handling.