/debank/protocols/holders

POST /api/debank/protocols/holders

Price: 1 credit

Get the top depositors of a DeFi protocol by its protocol id

How to use it

Reverse lookup: get the largest depositors / users of a DeFi protocol by its DeBank protocol id (uniswap3, aave3, lido, etc.). Returns each holder wallet with the USD value it has deposited in the protocol, its share and cumulative share of the protocol's total value, the main tokens it deposited, and its DeBank profile (web3 id, display name, total portfolio USD value, follower count, VIP flag, avatar), ordered from largest down. Useful for finding the biggest LPs and depositors of a protocol.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — DeBank protocol id (e.g. uniswap3, aave3, lido)
• count integer required — Max number of top holders to return (min: 1)

Response

• @type string (default: "DebankProtocolHolder")
• id string required
• web3_id string nullable
• name string nullable
• portfolio_usd_value number nullable
• follower_count integer nullable
• is_vip boolean (default: false)
• image string nullable
• usd_value number nullable
• share number nullable
• cumulative_share number nullable
• top_tokens array (default: [])
  • @type string (default: "DebankDepositToken")
  • id string nullable
  • symbol string nullable
  • chain string nullable
  • amount number nullable
  • price number nullable
  • usd_value number nullable
  • image string 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.