/defillama/pools/search

POST /api/defillama/pools/search

Price: 20 credits

Search DeFiLlama yield pools with optional chain/project/stablecoin/APY/TVL filters

How to use it

Search DeFi yield-farming pools tracked by DeFiLlama, with optional filters by blockchain, project, stablecoin-only, minimum APY, and minimum TVL. Returns each pool's id, chain, project, token symbol, pool metadata, total value locked, APY (base/reward/mean), recent APY changes over 1/7/30 days, 1-day and 7-day trading volume, impairment-loss risk, exposure, reward and underlying tokens, and an APY trend prediction.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Number of pools to return (min: 1)
• chain string nullable — Filter by blockchain name (examples: "Ethereum", "Arbitrum")
• project string nullable — Filter by project (examples: "lido", "aave-v3")
• stablecoin boolean nullable — Filter to stablecoin pools only
• min_apy number nullable — Minimum APY (percent) (min: 0)
• min_tvl number nullable — Minimum TVL in USD (min: 0)

Response

• @type string (default: "DefillamaPool")
• pool string required
• chain string nullable
• project string nullable
• symbol string nullable
• tvl_usd number nullable
• apy number nullable
• apy_base number nullable
• apy_reward number nullable
• apy_mean_30d number nullable
• apy_pct_1d number nullable
• apy_pct_7d number nullable
• apy_pct_30d number nullable
• volume_usd_1d number nullable
• volume_usd_7d number nullable
• is_stablecoin boolean (default: false)
• il_risk string nullable
• exposure string nullable
• pool_meta string nullable
• reward_tokens array (default: [])
• underlying_tokens array (default: [])
• predictions object nullable
  • @type string (default: "DefillamaPoolPrediction")
  • predicted_class string nullable
  • predicted_probability number nullable
  • binned_confidence integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.