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 DiscordNet token flow to and from centralized-exchange wallets — deposits (often bearish, incoming sell-side liquidity) versus withdrawals (often bullish, coins leaving for cold storage). Tracked per symbol across Ethereum, BSC, Base, Arbitrum, Optimism, Tron and Solana, plus native BTC and ETH.
Wallets tracked across Binance, Coinbase, Kraken, Bybit and OKX · 67 tokens with live flow. Full-universe coverage and per-chain breakdowns are available on the API (Free); spike-alert polling on Pro. Hourly flow history back to May 2026 is on /exchange-flows/{symbol}/history.
Coins move to an exchange to be sold; they leave to be held.
A deposit is a token moving from a self-custody or unknown wallet into a known centralized-exchange wallet — the precondition for a sale, so a sustained rise in deposits is often read as bearish, incoming sell pressure. A withdrawal is the reverse: coins leaving an exchange for cold storage, which removes them from immediate sell-side liquidity and is often read as bullish.
Flow direction is a leading, not confirming signal — it front-runs the trade, not the price move. A single large deposit can also be an exchange-to-exchange transfer or an OTC settlement rather than a sale, so the spike z-score above matters more than any one transfer: it flags flow that is statistically unusual against that symbol's own recent baseline, not just large in absolute terms.
curl -H "X-API-Key: cdk_live_yourkey" \ "https://cryptodataapi.com/api/v1/on-chain/exchange-flows/BTC"
Full-universe per-symbol flow, per-chain breakdowns, hourly history back to 28 May 2026 and spike-alert polling are available on the exchange flows endpoint docs. Every large transfer since 8 Oct 2026 is archived as exchange_flow_spikes on backtest data.
Flow data is noisy at the single-transfer level — most deposits are routine, not signals. The prompt below forces an agent to define what makes a flow event actionable (statistical unusualness plus a size floor) before it ever proposes a trade.
Build me an exchange-flow whale-alert monitor on CryptoDataAPI data.
Poll /api/v1/on-chain/exchange-flows/spike-alerts on a short interval and treat a row as actionable only when spike_zscore_1h (from /api/v1/on-chain/exchange-flows/{symbol}) is beyond +-2 for that same symbol AND the notional clears a minimum USD floor you choose per symbol tier (majors need a much higher floor than long-tail tokens).
Decide explicitly how you'd act on a confirmed deposit spike versus a confirmed withdrawal spike, and over what horizon you expect the signal to matter (minutes for a scalp, days for a positioning bias) — justify the choice against the fact that flow is a leading indicator, not a confirming one.
Report false-positive rate against next-1h price direction, and show whether filtering to only the highest-z, highest-notional spikes improves the hit rate versus taking every alert.