Get token holders with balances and identity info for any ERC-20 across 60+ chains.
What it does
The Zapper Token Holders endpoint returns a paginated list of holders for a specific ERC-20 token on a given chain. For each holder, the response includes the wallet address, their percentage share of the token supply, the value of their holdings, and identity information (ENS, Farcaster profile, display name). The endpoint also returns token metadata such as name, symbol, decimals, and image URL.
This is one of 16+ paid tools in the Zapper x402 API suite, which covers onchain data across 60+ chains including token prices, NFTs, portfolios, transactions, DeFi balances, and social identity. The token-holders endpoint accepts a POST request with the token contract address, chain ID, and a count of holders to return. Pagination is supported via cursor-based `after` parameter.
Payment is handled via the x402 protocol on Base (chain 8453) using USDC. Each call costs 1,125 base units of USDC (6 decimals), which equals $0.001125 per request. The endpoint is live and returns a proper 402 challenge when called without payment.
Capabilities
Use cases
- —Analyze token holder distribution and concentration for a specific ERC-20 token
- —Identify top holders of a token by percentage share and value
- —Resolve holder identities (ENS, Farcaster, Basenames) for whale tracking
- —Build token holder leaderboards or dashboards
- —Monitor changes in holder composition over time by polling the endpoint
Fit
Best for
- —Agents or apps that need real-time token holder data across 60+ EVM chains
- —Whale-watching and holder concentration analysis
- —Enriching wallet addresses with social identity (ENS, Farcaster)
- —Building portfolio analytics tools that need holder context
Not for
- —Non-EVM chains (Solana, Bitcoin, etc.)
- —Historical snapshots of holder data at a past block height (endpoint appears to return current state only)
- —Free or unauthenticated access — requires x402 USDC payment per call
Quick start
curl -X POST https://public.zapper.xyz/x402/token-holders \
-H "Content-Type: application/json" \
-H "X-Payment: <x402-payment-token>" \
-d '{"address":"0x833589fcd6edb6e08f4c7c32d4f71b54bda02913","chainId":8453,"first":10}'Example
Request
{
"first": 10,
"address": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
"chainId": 8453
}Response
{
"data": {
"fungibleTokenV2": {
"name": "USD Coin",
"symbol": "USDC",
"address": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
"holders": {
"edges": [
{
"node": {
"value": 12500000.5,
"account": {
"displayName": {
"value": "vitalik.eth"
},
"farcasterProfile": {
"username": "vitalik"
}
},
"holderAddress": "0xabc...",
"percentileShare": 5.23
}
}
]
},
"decimals": 6,
"imageUrlV2": "https://..."
}
}
}Endpoint
Quality
Full OpenAPI schema with input/output descriptions, live 402 challenge captured, clear pricing, and example request body provided. Docked slightly because no actual 200 response example is available (output schema is illustrative only) and crawled docs pages returned 404s.
Warnings
- —The legacy Zapper REST API at /api is marked with a deprecation notice pointing to build.zapper.xyz; the x402 endpoints appear to be the current offering.
- —No actual 200 response sample was captured; the output schema in the probe is illustrative/structural only.
- —Documentation pages (/docs, /pricing, /README) all return 404.
Citations
- —Enterprise grade onchain data across 60+ chains — token prices, NFTs, portfolios, transactions, and more.https://public.zapper.xyz/x402/token-holders
- —Fixed price of 0.001125 (USD) per call, supporting x402 and MPP protocolshttps://public.zapper.xyz/x402/token-holders
- —Payment via USDC on Base (chain 8453), amount 1125 base units (= $0.001125)https://public.zapper.xyz/x402/token-holders
- —Legacy API deprecation notice directing users to build.zapper.xyzhttps://public.zapper.xyz/api