POST /api/defillama/protocols
Price: 20 credits
Get DeFiLlama protocol details by slug or protocol URL
Get full details of a DeFi protocol on DeFiLlama by its slug (e.g. 'aave', 'uniswap') or a DeFiLlama protocol URL. Returns name, symbol, description, website, social links, supported chains, current total value locked (TVL), per-chain TVL snapshot, market cap, audits, funding rounds, notable timeline events, and related sub-protocols.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)protocol string required — Protocol slug or a DeFiLlama protocol URL (examples: "aave", "uniswap", "lido", "https://defillama.com/protocol/aave"; minLength: 1)@type string (default: "DefillamaProtocol")id string requiredname string requiredsymbol string nullablealias string requiredurl string nullabledescription string nullableimage string nullablechains array (default: [])gecko_id string nullablecmc_id string nullabletwitter string nullablegithub array (default: [])address string nullabletreasury string nullablegovernance_id array (default: [])stablecoins array (default: [])audit_links array (default: [])category string nullablemcap number nullabletvl number nullableis_parent_protocol boolean (default: false)wrong_liquidity boolean (default: false)current_chain_tvls object (default: {})* numberother_protocols array (default: [])raises array (default: [])@type string (default: "DefillamaProtocolRaise")name string nullableround string nullableamount number nullabledate integer nullablesector string nullablecategory string nullablesource string nullablevaluation number nullablechains array (default: [])lead_investors array (default: [])other_investors array (default: [])hallmarks array (default: [])@type string (default: "DefillamaProtocolHallmark")date integer requiredtext string required422 — 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 — Protocol not found 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.