Rank the universe from strongest accumulation to heaviest distribution
API · /closestrength-api
Closing Strength (CLV) API
Where each market closes inside its daily range, and what that says about who is in control into the bell, computed live from Yahoo Finance daily OHLC — no key, nothing stored. The close is the most important price of the day: a market that runs up but closes back near its low was sold into all afternoon (distribution), while one that closes on its highs has buyers in firm control (accumulation), even if the headline change is the same. The Close Location Value (CLV) captures this on a -1 to +1 scale — +1 is a close exactly on the high, -1 exactly on the low, 0 the middle of the range. This API turns it into a conviction gauge. For each instrument it returns today's CLV, the average CLV over the window (a positive average means closes persistently in the upper half — accumulation; negative means distribution), the recent 20-day CLV as the current pressure reading, the share of days that closed in the upper third versus the lower third of their range, and a plain-language read. The asset endpoint returns one instrument's full closing-strength profile; the screener endpoint ranks the cross-asset universe from strongest accumulation to heaviest distribution, so you can see where buyers are quietly winning the close. This is the close-location / accumulation-distribution-pressure cut, price-only and no volume — distinct from the candlestick-pattern API (named shapes on the last bar), the volume-indicator tools and the price feeds. It is who won the day.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 250 ms
- Server probes · 24h
- Subscribers
- 4,737
- active
- Total calls
- 4
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 725 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 725 calls/month
- 2 req/sec
- All endpoints
- No credit card
Starter
€10.70 /month
- 15,700 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 15.7k calls/month
- 6 req/sec
- All metrics & classes
- Email support
Pro
€34.60 /month
- 85,500 calls / month
- 16 requests / second
- Hard cap (429 above quota, no overage)
- 85.5k calls/month
- 16 req/sec
- Priority support
Mega
€78.20 /month
- 478,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 478k calls/month
- 40 req/sec
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Candlestick Pattern Screener (Multi-Asset) API
Which markets just printed a reversal or continuation candlestick pattern on their latest daily candle, computed live from Yahoo Finance (no key, nothing stored). Candlestick patterns are the oldest price-action signals there are: a hammer at a low hints a bounce, a shooting star at a high a turn, an engulfing candle a momentum shift. For a cross-asset, cross-sector universe — equity indices and sectors, gold, oil, commodities, bonds and crypto — this reads each asset's most recent candles and detects the classic single- and two-candle patterns (doji, hammer, inverted hammer, shooting star, hanging man, bullish/bearish engulfing, bullish/bearish harami, marubozu), tagging each bullish, bearish or neutral. The screener endpoint returns every market flashing a pattern right now, split into bullish and bearish signals. The asset endpoint returns one market's latest candle with any pattern detected on it. The patterns endpoint lists what is recognised. The cross-asset candlestick-pattern screener cut — distinct from the crypto-only pattern detector and the bring-your-own-candle pattern API. It scans the whole market for price-action signals at once.
api.oanor.com/candlestickscreener-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
Variance Ratio Test API
A formal statistical test of whether a market follows a random walk, or whether its returns carry tradeable momentum or mean-reversion that is real rather than noise — the Lo-MacKinlay variance ratio test, computed live from Yahoo Finance daily closes, no key, nothing stored. Most persistence tools give you a single descriptive number; this gives you a hypothesis test with a verdict. The variance ratio compares the variance of multi-day returns to the variance of one-day returns scaled up: under a true random walk the ratio is 1 at every horizon. A ratio above 1 means returns positively autocorrelate (trends persist — momentum); below 1 means they reverse (mean-reversion). Crucially it attaches a heteroskedasticity-robust z-statistic and a p-value at each horizon, so you know whether the deviation from a random walk is statistically significant or just sampling noise — the thing a point estimate cannot tell you. The asset endpoint runs the test at horizons of 2, 4, 8 and 16 days and returns each ratio, z-statistic, p-value and a reject/fail-to-reject verdict, plus an overall read. The screener endpoint ranks the cross-asset universe by their 2-day variance ratio, separating the statistically momentum-like markets from the mean-reverting ones. This is the random-walk hypothesis-test cut — distinct from the Hurst-exponent regime API (a point estimate with no significance), the momentum and the price APIs. It is the test, with the p-value attached.
api.oanor.com/varianceratio-api
Calendar Effects (Day-of-Week & Turn-of-Month) API
The two best-documented calendar anomalies in equities — the day-of-week effect and the turn-of-month effect — measured live across a cross-asset universe from Yahoo Finance daily history, no key, nothing stored. Decades of research show returns are not spread evenly through the week or the month: the turn-of-month effect — the cluster of the last trading day of a month and the first few of the next — has historically captured the bulk of the entire month's gain while the rest of the month drifts; and the day-of-week effect (the old "Monday effect" and its kin) shows some weekdays running persistently stronger than others. This API quantifies both directly. The turnofmonth endpoint splits an instrument's history into the turn-of-month window (the last trading day plus the first three of each month) versus the rest, and returns the average daily return and win-rate of each, the spread between them, and the share of the total return earned inside that handful of days. The dayofweek endpoint returns, for each weekday, the average daily return, win-rate and sample size, with the best and worst day. The screener endpoint ranks the cross-asset universe by the strength of the turn-of-month effect, so you can see where the calendar edge is biggest. This is the day-of-week / turn-of-month calendar-anomaly cut — distinct from the month-of-year seasonality APIs (equity-index, FX, commodity) and the crypto-only intraday/day-of-week seasonality API. Patterns are descriptive, not predictive.
api.oanor.com/calendareffects-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Closing Strength (CLV) API?
What's the rate limit for Closing Strength (CLV) API?
How much does Closing Strength (CLV) API cost?
Can I cancel my subscription anytime?
Is Closing Strength (CLV) 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/closestrength-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/closestrength-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/closestrength-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/closestrength-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.