/defillama/fees

POST /api/defillama/fees

Price: 10 credits

Get DeFiLlama protocol fees and revenue summary by slug or fees URL

How to use it

Get the fees and revenue summary of a DeFi protocol on DeFiLlama by its slug (e.g. 'uniswap', 'aave', 'lido') or a DeFiLlama fees URL. Returns the protocol's name, category, supported chains, logo, total fees generated over 24 hours, 7 days, 30 days, 1 year and all time, daily change, and a per-chain breakdown of those totals.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• protocol string required — Protocol slug or a DeFiLlama fees URL (examples: "uniswap", "aave", "lido", "https://defillama.com/fees/uniswap"; minLength: 1)

Response

• @type string (default: "DefillamaProtocolFees")
• id string required
• name string required
• alias string required
• category string nullable
• description string nullable
• image string nullable
• chains array (default: [])
• parent_protocol string nullable
• child_protocols array (default: [])
• methodology_url string nullable
• total_24h number nullable
• total_7d number nullable
• total_30d number nullable
• total_1y number nullable
• annualized_1y number nullable
• total_all_time number nullable
• change_1d number nullable
• chain_breakdown array (default: [])
  • @type string (default: "DefillamaFeesChainBreakdown")
  • chain string required
  • total_24h number nullable
  • total_7d number nullable
  • total_30d number nullable
  • total_1y number nullable
  • total_all_time number nullable
  • average_1y number nullable
  • change_1d number nullable
  • change_7d number nullable
  • change_30d number 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 — 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.

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.