/debank/users/history

POST /api/debank/users/history

Price: 1 credit

Get a wallet's transaction history across all chains, by address

How to use it

Get the on-chain transaction history of a crypto wallet by its EVM address (0x...), newest first. Returns each transaction with its hash, chain, operation type (receive, send, approve, contract interaction, etc.), timestamp, the interacted protocol or counterparty address, the gas fee in USD, and the token transfers involved (direction, token, amount, USD value). Optionally restrict to a single chain.

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")
• count integer required — Max number of transactions to return (min: 1)
• chain string nullable — Restrict to a single chain by its DeBank chain id (e.g. eth, bsc, base)

Response

• @type string (default: "DebankHistoryItem")
• id string required
• chain string nullable
• type string nullable
• time_at integer nullable
• project_id string nullable
• other_addr string nullable
• gas_usd_value number nullable
• transfers array (default: [])
  • @type string (default: "DebankHistoryTransfer")
  • direction string required
  • amount number nullable
  • token_id string nullable
  • symbol string nullable
  • usd_value number nullable
  • image string nullable
• token_approve object nullable
  • @type string (default: "DebankTokenApprove")
  • token_id string nullable
  • symbol string nullable
  • image string nullable
  • spender string nullable
  • amount 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 — 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.