We're building the most comprehensive crypto data API we can, and it's still growing — there's always a coin, a field or an endpoint we haven't got to yet.
Please tell us about any data you think Crypto Data API should nail but doesn't. We're data nerds who love to geek out about market data, trading bots, AI agents, or how to make your trading stack work in general. Prefer a form? Send feedback.
— Sam and the CDA team
Join us on DiscordHow much of each token is actually trading, how much is still locked, and when the next vesting cliff lands. A coin at a 22% float has four fifths of its supply still to come — its market cap prices a fraction of the eventual supply.
Float is circulating supply divided by the token's maximum supply where one is defined, else its total supply — the API returns supply_basis so you always know which. Overhang is the dollar value of everything not yet circulating, as a multiple of current market cap: above 1.0x there is more value locked than the market currently prices. "Not tracked" does not mean no unlock is scheduled — it means no vesting schedule is published for that token in our source. Do not read it as safe.
A token unlock is a scheduled date when tokens held under vesting — team, early investors, the ecosystem treasury — become transferable. It adds sellable supply without adding demand, which is why a large cliff on a thin float is worth knowing about in advance rather than in hindsight.
The size that matters is not the token count but its share of what is already trading. Ten million tokens unlocking into a float of twenty million is a different event from the same ten million landing on a float of two billion, so every cliff here is expressed as a percentage of circulating supply as well as in dollars.
This is a cliff calendar, not an emissions feed. Steady inflation — mining rewards, linear vesting, a fixed daily release — is deliberately excluded: it is a drip, not a step, and listing it would bury the events that actually move a market.
curl -H "X-API-Key: cdk_live_yourkey" \ "https://cryptodataapi.com/api/v1/supply/float" curl -H "X-API-Key: cdk_live_yourkey" \ "https://cryptodataapi.com/api/v1/supply/unlocks?window_days=30"
/supply/float returns float, locked supply, dilution overhang and the next unlock per coin; /supply/unlocks returns the forward calendar. See the token supply endpoint docs.
An unlock calendar is forward-looking, which makes it the one dataset you cannot reconstruct after the fact: vesting schedules get revised, and a schedule pulled today tells you nothing about what the market could actually see three months ago. So we snapshot the whole board on a timer. The archive is a point-in-time record — float, locked supply, dilution overhang and the next dated cliff, as published on each day — which is what an event study around an unlock actually needs.
curl -H "X-API-Key: cdk_live_yourkey" \ "https://cryptodataapi.com/api/v1/backtesting/snapshots?data_type=token_unlocks&start=2026-08-20"
The snapshot series starts the day it shipped and grows forward — a schedule that was never recorded cannot be recovered from DefiLlama, which serves only the current version. The live /supply/unlocks and /supply/float endpoints remain the right call for "what is coming"; this archive answers "what did we know, and when".