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 RSI & Oscillator Screener API
Which coins are overbought or oversold right now, computed live from Binance candles — no key, nothing stored. Momentum oscillators are the classic mean-reversion signals: a Relative Strength Index (RSI) above 70 says a coin is overbought and stretched, below 30 oversold and washed out, while the Stochastic oscillator times the turn within the recent range. The oscillators endpoint fetches a pair's candles and returns its Wilder RSI(14), the Stochastic %K and %D, and a plain signal (overbought, oversold or neutral) on a chosen timeframe. The screener endpoint scans a basket of coins and surfaces the ones that are currently overbought (possible pullback) and oversold (possible bounce), ranked by how stretched they are. The symbols endpoint lists tradable pairs. This is the coin-native oscillator / mean-reversion screener cut for crypto — it fetches the live data itself, distinct from the generic oscillator calculators (which you feed your own OHLC), the momentum trend-alignment, the Donchian breakout and the candlestick-pattern APIs in the catalogue. Pairs are Binance symbols (BTCUSDT) or a coin=BTC"e=USDT form; interval is 1h/4h/1d/1w.
api.oanor.com/cryptorsi-api
Crypto Candlestick Pattern Detector API
Which reversal and continuation candlestick patterns have just printed on a coin, and which coins across the market are flashing one right now, detected live from Binance candles — no key, nothing stored. Candlestick patterns are the oldest price-action signals there are: a hammer at the bottom of a move, a bearish engulfing at the top, a doji marking indecision. The detect endpoint fetches a pair's recent candles and returns the patterns found on the latest ones — each with its name, whether it is bullish, bearish or neutral, the candle it formed on and a short meaning — plus the latest OHLC. The screener endpoint scans a basket of coins and surfaces the ones whose most recent completed candle just formed a bullish or bearish reversal pattern, so you can find fresh setups across the market in one call. The symbols endpoint lists tradable pairs. This is the coin-native candlestick-pattern screener cut for crypto — it fetches the live data itself, distinct from the generic pattern-recognition calculator (which you feed your own OHLC), the Donchian breakout, the momentum and the volume-profile APIs in the catalogue. Detected patterns include hammer, shooting star, bullish/bearish engulfing, doji, marubozu and morning/evening star. Pairs are Binance symbols (BTCUSDT) or a coin=BTC"e=USDT form; interval is 1h/4h/1d/1w.
api.oanor.com/cryptopatterns-api
Crypto Multi-Timeframe Momentum API
Whether a coin is trending the same way across every timeframe, computed live from Binance candles — no key, nothing stored. A single 24-hour change is noise; what traders want is alignment — when the 1-hour, 4-hour, 1-day, 1-week and 1-month returns all point the same direction, that is a strong, coherent trend, and when they disagree the move is choppy or turning. The momentum endpoint returns, for one coin, the percent change over each of those five horizons, the up/down direction of each, an alignment score (how strongly the timeframes agree, from -1 fully bearish to +1 fully bullish) and an overall bias label. The screener endpoint scans a basket and ranks the coins by aligned momentum, surfacing the strongest coherent uptrends (every timeframe up) and downtrends (every timeframe down). The symbols endpoint lists tradable pairs. This is the multi-timeframe momentum / trend-alignment cut for crypto — distinct from the single-window movers, the Donchian breakout screener, the FX-pivot and the generic indicator-calculator APIs in the catalogue. Pairs are Binance symbols (BTCUSDT) or a coin=BTC"e=USDT form; horizons are fixed at 1h/4h/24h/7d/30d.
api.oanor.com/cryptomomentum-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.