/debank/users

POST /api/debank/users

Price: 1 credit

Get a wallet's DeBank profile and multichain net worth by address

How to use it

Get the full DeBank profile of a crypto wallet by its EVM address (0x...). Returns the wallet's total net worth in USD, per-blockchain value breakdown, social profile (web3 id, bio, follower and following counts, DeBank rank, trust count, linked Twitter handle, VIP/pro status), reputation tags, the chains the wallet is active on, and a summary of its largest token, protocol and NFT-collection holdings. Use the tokens, protocols and history endpoints for the full holdings and transaction list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Wallet address (EVM 0x address) (examples: "0xd8da6bf26964af9d7eed9e03e53415d37aa96045")

Response

• @type string (default: "DebankUser")
• id string required
• name string nullable
• web3_id string nullable
• image string nullable
• bio string nullable
• born_at integer nullable
• usd_value number nullable
• tvf number nullable
• rank integer nullable
• follower_count integer nullable
• following_count integer nullable
• trust_count integer nullable
• trust_count_7d integer nullable
• twitter_id string nullable
• is_vip boolean (default: false)
• is_pro boolean (default: false)
• is_spam boolean nullable
• is_scam boolean nullable
• is_contract boolean (default: false)
• tags array (default: [])
• used_chains array (default: [])
• chains array (default: [])
  • @type string (default: "DebankChainBalance")
  • id string required
  • name string nullable
  • usd_value number nullable
  • native_token_id string nullable
  • community_id integer nullable
  • image string nullable
• top_coins array (default: [])
  • @type string (default: "DebankTopToken")
  • id string nullable
  • symbol string nullable
  • chain string nullable
  • amount number nullable
  • price number nullable
  • usd_value number nullable
  • portfolio_percent number nullable
  • image string nullable
• top_tokens array (default: [])
  • @type string (default: "DebankTopToken")
  • id string nullable
  • symbol string nullable
  • chain string nullable
  • amount number nullable
  • price number nullable
  • usd_value number nullable
  • portfolio_percent number nullable
  • image string nullable
• top_protocols array (default: [])
  • @type string (default: "DebankTopProtocol")
  • id string nullable
  • name string nullable
  • chain string nullable
  • usd_value number nullable
  • portfolio_percent number nullable
  • image string nullable
• top_collections array (default: [])
  • @type string (default: "DebankTopCollection")
  • id string nullable
  • name string nullable
  • chain string nullable
  • item_count integer nullable
  • rank integer 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 — Wallet 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.