/defillama/protocols/search

POST /api/defillama/protocols/search

Price: 20 credits

Search and list DeFiLlama protocols with optional name, category, and chain filters

How to use it

List DeFi protocols tracked by DeFiLlama, optionally filtered by a name substring, an exact category, or a supported chain. Each result is a lightweight protocol card with slug, symbol, category, supported chains, current total value locked (TVL), market cap, price changes, and social links. Use the slug from a result to fetch full protocol details.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of results (min: 1)
• query string nullable — Filter protocols by name (case-insensitive substring)
• category string nullable — Filter protocols by exact category
• chain string nullable — Filter protocols by supported chain

Response

• @type string (default: "DefillamaProtocolListItem")
• id string required
• name string required
• alias string nullable
• symbol string nullable
• category string nullable
• chain string nullable
• chains array (default: [])
• url string nullable
• description string nullable
• image string nullable
• gecko_id string nullable
• cmc_id string nullable
• twitter string nullable
• tvl number nullable
• change_1h number nullable
• change_1d number nullable
• change_7d number nullable
• mcap number nullable
• listed_at 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.