Get Token Holders Chart
Retrieves historical token holder count chart data by network and contract address. Returns time series showing holder changes over 7 days, 30 days, or all time ('max'). Ideal for: tracking holder growth, identifying accumulation/distribution phases, measuring token adoption.
Catalog action Blockchain Data
Retrieves historical token holder count chart data by network and contract address. Returns time series showing holder changes over 7 days, 30 days, or all time ('max'). Ideal for: tracking holder growth, identifying accumulation/distribution phases, measuring token adoption.
At a Glance
| Field | Value |
|---|---|
| Action ID | coingecko-get-token-holders-chart |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | coingecko, onchain, token, holders, chart, historical, read |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
network | string | Yes | Network ID (e.g., 'eth', 'base', 'solana'). |
tokenAddress | string | Yes | Token contract address. |
days | string | No | Days of data: '7' (all data), '30' (daily), or 'max' (weekly). Default: 7. |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
tokenAddress | string | Yes | Token contract address. |
tokenName | string | null | No | Token name. |
tokenSymbol | string | null | No | Token symbol. |
coingeckoCoinId | string | null | No | CoinGecko coin ID. |
holdersChart | array | Yes | Historical holder count data points. |
Examples
json{ "type": "coingecko-get-token-holders-chart", "payload": { "network": "example-network", "tokenAddress": "0x0000000000000000000000000000000000000000" }, "children": []}
bashcurl -X POST "https://api.b3os.org/v1/actions/coingecko-get-token-holders-chart/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "network": "example-network", "tokenAddress": "0x0000000000000000000000000000000000000000" }}'
Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.