---
title: "Get day-by-day holder count history for an ERC-20 token"
method: POST
path: "/?ankr_getTokenHoldersCount"
tags: ["Token API"]
---

# Get day-by-day holder count history for an ERC-20 token

`POST /?ankr_getTokenHoldersCount`

## Request

- Base URL: `https://rpc.ankr.com/multichain/569ca1f392f7d3d0bb1073a1173ecb649af1d9249231fe59fa95db19d5ae41fe`
- URL: `https://rpc.ankr.com/multichain/569ca1f392f7d3d0bb1073a1173ecb649af1d9249231fe59fa95db19d5ae41fe/?ankr_getTokenHoldersCount`
- Auth: none declared
- TypeScript: <https://skmtc.dev/ankr/apis/ankr-advanced-api/docs/%3Fankr_getTokenHoldersCount/post.ts> (a function with typed inputs; its response is checked against the schema)

Returns the per-day count of unique holders for the specified ERC-20 token, along with the total token amount on-chain at each snapshot. Useful for charting distribution trends or feeding token-analytics dashboards.

Pass `contractAddress` of the token plus the `blockchain` it lives on. The history is paginated; use `pageSize` (default `10000`, max `10000`) and `pageToken` to walk further back in time. `latestHoldersCount` is the most recent week's count.

Part of the **Token API** product (700 compute units per call, $0.00007 at base rate).

## Request body

- object
  - `id` integer, required: Client-supplied request ID echoed in the response.
  - `jsonrpc` '2.0', required
  - `method` 'ankr_getTokenHoldersCount', required
  - `params` object, required
    - `blockchain` 'arbitrum' | 'avalanche' | 'base' | 'bsc' | 'eth' | 'fantom' | 'flare' | 'gnosis' | 'linea' | 'optimism' | 'polygon' | 'scroll' | 'somnia_mainnet' | 'taiko' | 'telos' | 'xlayer' | 'avalanche_fuji' | 'base_sepolia' | 'eth_sepolia' | 'optimism_sepolia' | 'polygon_amoy', required: Target blockchain identifier.
    - `contractAddress` string, required: Token contract address.
    - `pageSize` integer: Entries per page. Default `10000`, max `10000`.
    - `pageToken` string: Opaque page token from a prior response's `nextPageToken`.

## Response `200`

Success. JSON-RPC `result` carries the daily history and the latest holder count. JSON-RPC errors are returned with HTTP 200; check the response body for an `error` key.

- object
  - `id` integer, required
  - `jsonrpc` '2.0', required
  - `result` object, required
    - `blockchain` 'arbitrum' | 'avalanche' | 'base' | 'bsc' | 'eth' | 'fantom' | 'flare' | 'gnosis' | 'linea' | 'optimism' | 'polygon' | 'scroll' | 'somnia_mainnet' | 'taiko' | 'telos' | 'xlayer' | 'avalanche_fuji' | 'base_sepolia' | 'eth_sepolia' | 'optimism_sepolia' | 'polygon_amoy', required
    - `contractAddress` string, required
    - `tokenDecimals` integer, required
    - `latestHoldersCount` integer, required: Most recent week's holder count.
    - `nextPageToken` string, required
    - `holderCountHistory` object[], nullable, required: Per-day snapshots (newest first).
      - `holderCount` integer: Distinct holders that day.
      - `lastUpdatedAt` string: Snapshot timestamp (ISO 8601).
      - `totalAmount` string: Human-readable total token amount on-chain.
      - `totalAmountRawInteger` string: Raw integer total (`value × 10^decimals`).

## Other responses

- `400`: Bad Request — malformed JSON-RPC envelope or invalid `params`. The gateway rejects before the JSON-RPC layer processes the call.
- `401`: Unauthorized — missing or invalid API key in the server URL path. Verify that `{API_KEY}` is set to a valid project key.
- `429`: Too Many Requests — the API key has exceeded its rate or quota limits. Back off and retry; consider upgrading the Premium tier for higher limits.
- `500`: Server error — unexpected condition. Retry with exponential backoff; if it persists, file a ticket at https://www.ankr.com/support/.

---

[API](https://skmtc.dev/ankr/apis/ankr-advanced-api.md) - [All operations](https://skmtc.dev/ankr/apis/ankr-advanced-api/llms.txt) - [OpenAPI document](https://skmtc.dev/ankr/apis/ankr-advanced-api/revisions/77e494aeec1b?raw)