Skip to main content
Composer activates automatically when toToken is set to a supported protocol token address. No additional parameters are needed.

​
How toToken Triggers Composer

When toToken corresponds to a supported vault/staking/deposit token, LI.FI’s routing engine automatically:
  1. Identifies this as a Composer route
  2. Finds the optimal path (swap, bridge, or both) to acquire the underlying asset
  3. Compiles the Composer instructions (eDSL → bytecode)
  4. Simulates the full execution path
  5. Returns a transactionRequest ready to sign

​
Composer as a Tool

Composer is classified as a tool in the LI.FI API, similar to bridges and DEX aggregators. Composer routes appear alongside bridge and swap routes in API responses. As with any LI.FI tool, integrators can use allowTools / denyTools to include or exclude Composer from their routing preferences.

​
Full Parameter Reference

For complete endpoint documentation, parameter lists, and authentication details, see:

GET /quote

Single-step quote endpoint with all parameters

POST /advanced/routes

Multi-route endpoint with all parameters

Quote vs Route

When to use each endpoint

API Overview

Base URL, authentication, and rate limits

API Integration Guide

Step-by-step Composer integration walkthrough

Error Handling

Handle Composer-specific errors

Supported Protocols

Full list of supported vault/staking tokens

Status Tracking

Track transaction status after execution