/zerion/wallets/positions

POST /api/zerion/wallets/positions

Price: 20 credits

Get a wallet's token and DeFi positions across all blockchain networks

How to use it

Get the individual holdings of a crypto wallet by its EVM address (0x...) or ENS name. Returns every fungible position across all supported chains, ordered by USD value: simple wallet token balances and DeFi positions (deposited, staked, locked, rewards, loans). Each item has the asset (name, symbol, icon, verification, per-chain contract addresses), the chain, the human-readable amount, the value in the chosen currency, the position type, and the owning DeFi app when applicable. Optionally filter by chain.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• address string required — Wallet address: an EVM 0x address or an ENS / identity name (examples: "0xd8da6bf26964af9d7eed9e03e53415d37aa96045", "vitalik.eth")
• count integer required — Max number of positions to return (min: 1)
• currency string — Currency to denominate position values in (default: "usd"; one of: "usd", "eur", "gbp", "jpy", "aud", "cad", "chf", "cny", "inr", "krw", "rub", "brl", "try", "btc", "eth")
• chains array nullable — Filter positions to these blockchain networks (one of: "ethereum", "tron", "binance-smart-chain", "base", "arbitrum", "plasma", "ink", "avalanche", "polygon", "monad", "optimism", "mantle", "katana", "berachain", "xdai", "megaeth", "sei", "okbchain", "linea", "fraxtal", "blast", "unichain", "sonic", "celo", "zksync-era", "scroll", "abstract", "ronin", "bob", "xinfin-xdc", "soneium", "fantom", "cronos-zkevm", "manta-pacific", "aurora", "taiko", "metis-andromeda", "ape", "mode", "opbnb", "somnia", "lisk", "tomochain", "polynomial", "polygon-zkevm", "0g", "lens", "gravity-alpha", "zora", "swellchain", "redstone", "astar-zkevm", "rari", "degen", "cyber", "hyperevm", "solana", "tempo", "wonder", "world", "zero", "zkcandy", "zklink-nova", "re-al")

Response

• @type string (default: "ZerionPosition")
• id string required
• name string nullable
• type string nullable
• protocol string nullable
• value number nullable
• amount number nullable
• is_displayable boolean nullable
• is_included_in_chart boolean nullable
• updated_at string nullable
• chain object nullable
  • @type string (default: "ZerionChainRef")
  • id string required
  • name string nullable
  • image string nullable
  • is_testnet boolean nullable
• asset object nullable
  • @type string (default: "ZerionAsset")
  • id string nullable
  • name string nullable
  • symbol string nullable
  • image string nullable
  • price number nullable
  • price_change_24h number nullable
  • is_verified boolean nullable
  • contracts object (default: {})
    • * string
• dapp object nullable
  • @type string (default: "ZerionDapp")
  • id string nullable
  • name string nullable
  • image string nullable
  • url 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 or ENS name 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.