Order flow, delta & CVD for a pair
API · /orderflow-api
Crypto Order Flow & CVD API
Who is actually hitting the market — buyers or sellers — read live from Binance's aggregated trade tape, no key, nothing stored. Every trade carries a flag for which side was the aggressor: a taker buy lifts the ask, a taker sell hits the bid. Summing those over a window gives order flow — the net buying or selling pressure that price action follows — and its running total is the Cumulative Volume Delta (CVD), the metric order-flow traders watch to spot absorption and divergence. The flow endpoint scans the recent aggregated trades for a pair (up to 5,000) and returns the taker-buy and taker-sell volume in base and quote, the delta (buy minus sell), the CVD over the window, the buy/sell ratio, the share of volume that was buying, a net-pressure label and the time span covered. The large endpoint surfaces the big prints — single aggressive trades above a notional threshold — and tags each as a taker buy or sell, so you see the whale orders moving the tape, with the buy- and sell-side large-trade totals. The symbols endpoint lists tradable pairs. This is the trade-flow / CVD microstructure analytics cut for crypto — distinct from the raw recent-trades feed, the order-book depth and the price, ticker and slippage APIs in the catalogue. Pairs are Binance symbols (BTCUSDT) or a coin=BTC"e=USDT form.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 358 ms
- Server probes · 24h
- Subscribers
- 3,159
- active
- Total calls
- 4
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 450 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 450 calls/month
- 2 req/sec
- Flow + large + symbols
- No credit card
Starter
€12.18 /month
- 11,500 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 11,500 calls/month
- 6 req/sec
- Up to 5,000-trade CVD windows
- Email support
Pro
€37.44 /month
- 68,000 calls / month
- 18 requests / second
- Hard cap (429 above quota, no overage)
- 68,000 calls/month
- 18 req/sec
- Order-flow & whale-print pipelines
- Priority support
Business
€84.70 /month
- 360,000 calls / month
- 45 requests / second
- Hard cap (429 above quota, no overage)
- 360,000 calls/month
- 45 req/sec
- Trading-desk scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Crypto Trade Size Distribution API
Who is actually trading a pair — retail or whales — read from the composition of Binance's aggregated trade tape by trade size, no key, nothing stored. Order flow tells you the net direction; this tells you the size profile behind it: whether a move is driven by a swarm of small retail prints or a handful of large institutional ones, often the more important signal. The distribution endpoint scans the recent aggregated trades for a pair and buckets them into size cohorts (micro under $1k, retail $1k-$10k, mid $10k-$100k, whale over $100k), returning each cohort's trade count, volume in base and quote and its share of total volume, plus the whale-volume share — the single read on how institutional the flow is. The percentiles endpoint returns the trade-size percentiles (p50, p90, p99) and the average, median and largest trade. The symbols endpoint lists tradable pairs. This is the trade-size composition / participant-mix analytics cut for crypto — distinct from the order-flow / CVD API (which measures buy-versus-sell direction), the order-book depth, the slippage and the price APIs in the catalogue. Pairs are Binance symbols (BTCUSDT) or a coin=BTC"e=USDT form.
api.oanor.com/tradesize-api
Crypto Smart-Money vs Retail Positioning API
How crypto's biggest, most-capitalised futures traders are positioned versus the retail crowd — and the divergence between them — computed live from Binance's public futures positioning feed (no key, nothing stored). Binance splits its perpetual traders into the whole crowd and the "top traders" (the top ~20% of accounts by margin balance, a smart-money proxy) and publishes the long/short split of each. When smart money leans one way while the crowd leans the other, that gap is a classic contrarian signal: an over-long retail crowd the big accounts are quietly fading often marks a local top, and vice versa. The positioning endpoint returns, for a coin, the long/short ratio and long-share of three cohorts side by side — the global crowd, the top traders by account, and the top traders by position size. The divergence endpoint returns the smart-money-minus-retail gap with a plain-language read. The history endpoint returns the time-series across 5m to 1d buckets so you can watch the gap open and close. The smart-money-versus-retail / positioning-divergence cut for crypto — distinct from the single-cohort long/short-ratio feed, the funding-rate, open-interest and price APIs. It tells you who is on which side, not just how many are long.
api.oanor.com/smartmoney-api
Crypto-to-Macro Correlation API
Whether crypto is trading as a risk asset or a hedge, measured by how closely a coin moves with the stock market, gold and the dollar — computed live from Binance and Yahoo Finance, no key, nothing stored. The single most-asked macro question about crypto is whether it is "digital gold" or just high-beta tech; this answers it with numbers. The correlation endpoint returns, for a coin (BTC or ETH), its return correlation to the S&P 500, the Nasdaq 100, gold and the US dollar index over a chosen window, each with a plain-language read (risk-on if it tracks stocks, a hedge if it tracks gold or moves against the dollar) and an overall verdict. The beta endpoint returns the coin's beta to the S&P 500 — how much it amplifies equity moves — with the correlation and R-squared. This is the cross-asset / crypto-versus-traditional-markets correlation cut — distinct from the crypto-to-crypto correlation API (coins against each other), the realised-volatility and the price APIs in the catalogue. Correlations use daily log returns aligned on common trading days; coin is BTC or ETH, window 20-365 days.
api.oanor.com/cryptomacro-api
Crypto Funding Rate Arbitrage API
The perpetual-futures funding rate for a coin side by side across the major exchanges, and the spread between them — computed live from each venue's public API, no key, nothing stored. A perpetual swap charges or pays funding every few hours to keep its price tethered to spot; when the same coin's funding differs across exchanges, a trader can be long the perp where funding is most negative (and gets paid) and short where it is most positive, harvesting the spread market-neutral. The funding endpoint returns, for a coin, the current funding rate on Binance, Bybit, OKX and Gate.io — per interval and annualised — the venue paying the most, the one charging the most, and the cross-exchange spread (the arbitrage edge). The screener endpoint scans a basket and ranks the coins by the size of that spread, surfacing the biggest funding-arbitrage opportunities. This is the cross-exchange funding-rate / basis-arbitrage cut for crypto — distinct from the single-exchange funding-rates feed (one venue), the spot-versus-perpetual basis and the price APIs in the catalogue. Funding is per interval (most venues settle every 8 hours); annualisation assumes three settlements a day, and intervals can differ by venue, so verify before trading. Coins are bases (BTC, ETH).
api.oanor.com/fundingarbitrage-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Crypto Order Flow & CVD API?
What's the rate limit for Crypto Order Flow & CVD API?
How much does Crypto Order Flow & CVD API cost?
Can I cancel my subscription anytime?
Is Crypto Order Flow & CVD API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/orderflow-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/orderflow-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/orderflow-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/orderflow-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.