Yield Endpoints
Endpoints for retrieving liquidity pool information and APR data across multiple DEX protocols.
Retrieves detailed information about liquidity pools including APR, TVL, volume, and fee data.
Endpoint: POST /{chainId}/yield/pools
Path Parameters
- chainId (string, required): The blockchain network ID (e.g.,
1, 100)
Request Body
Array of pool addresses to query. Pass an empty array [] to fetch all available pools.
- Empty array returns all pools (up to result limit)
- With addresses returns only specified pools
- Maximum: 1000 pool addresses
Response Fields
Code Examples
Fetch all pools:
Fetch specific pools:
Response Example
Get Average APR by Project
Retrieves the average APR for each liquidity provider/DEX protocol.
Endpoint: GET /{chainId}/yield/pools-average-apr
Path Parameters
- chainId (string, required): The blockchain network ID (e.g.,
1, 100)
Code Examples
Response Example
Notes
Supported DEX Protocols
The API aggregates data from multiple liquidity providers:
- Uniswap V2/V3: Concentrated liquidity pools
- Balancer: Weighted and stable pools
- Curve: Stablecoin and wrapped token pools
- Sushiswap: AMM pools
- CoW AMM: Native CoW Protocol liquidity
- Others: Additional DEX protocols based on availability
APR Calculation
APR represents the yield liquidity providers earn through:
- Fee income: Trading fees collected by the pool
- Incentives: Token rewards (if applicable)
- Time period: Calculated over rolling time windows
- Precision: Rounded to 6 decimal places
TVL and Volume
Both metrics are denominated in USD:
- TVL: Snapshot of current liquidity
- Volume: 24-hour rolling trading volume
Result Limit
The pools endpoint has a maximum result limit of 1000 pools. When fetching all pools (empty array), results are limited to the top pools by TVL.
Caching
- Pools Average APR: Cached for 6 hours (21,600 seconds)
- Pools Info: Queries are cached at the database level for performance
Fee Tiers
Use Cases
Yield Comparison Dashboard:
Pool Selection for Liquidity:
Best Practices
- Cache appropriately: Respect cache headers to reduce load
- Batch queries: Request multiple pools in a single call
- Handle missing data: Some pools may have incomplete information
- Consider impermanent loss: APR doesn’t account for IL
- Verify data: Cross-reference with protocol interfaces for critical decisions
Last modified on March 4, 2026