Docs/Token data/Holders history

Holders history

GET/v1/token/{mint}/holders/historyPublic

Holder-count time series: one point per holder refresh, with the floor flag and the owner-aggregated top-10 concentration at each snapshot.

Path parameters

FieldTypeDescription
mintrequiredstringToken mint address (base58).

Query parameters

FieldTypeDescription
fromoptionalnumber (unix s)Window start. Defaults to to − 7 days.
tooptionalnumber (unix s)Window end. Defaults to now.
limitoptionalnumberMax points (≤1000; the newest points of the window are kept). default 1000
networkoptionalmainnet | devnetNetwork to read. Devnet returns an empty payload (with a note) until its ingestor lands. default mainnet

Response fields

FieldTypeDescription
from / tonumber (unix s)The resolved window actually queried.
items[].unixTimenumber (unix s)Snapshot time.
items[].countnumber | nullHolder count at that refresh (a lower bound when countIsFloor is true).
items[].countIsFloorbooleantrue = the bounded crawl capped at that refresh: the real count was >= count.
items[].top10OwnersPctnumber | nullOwner-aggregated, vault-excluded top-10 concentration at that refresh (see Security). null = unknown.
Points are appended on every holder refresh of a SUBSCRIBED mint: the scheduled keeper cycle (default every 15 min) plus the lazy on-request refresh — so cadence is roughly 15-minutely while a mint is subscribed. Mints nobody subscribes accrue no history (their cached /holders snapshot still refreshes). Mints refreshed before this feature shipped start their series at deploy time.
Snapshots are returned ascending (chart-friendly). When the window holds more than `limit` points, the NEWEST `limit` points are kept. History is retained for 90 days by default (operator-configurable).