Compute Technical Indicators
The technicals endpoints compute any of 80+ indicators (moving averages, oscillators, volatility and volume studies, regressions, Hilbert-transform cycles) for a list of tickers, on scanr.ai's own price history. You send tickers and parameters; you never send price data.
Use them to show why a stock matched a scan, to feed a model, or to chart studies without running your own TA library.
You'll need: a Power User or Business token.
One indicator
Each indicator has its own endpoint, POST /api/v2/technicals/technical/{category}/{name}. RSI is momentum/rsi:
The request
Values always end at the latest bar, which during market hours is the in-progress one. There is no date range.
Multi-output indicators
Some indicators produce several lines; outputs names them. MACD returns macd, macdsignal and macdhist; Bollinger Bands return upperband, middleband and lowerband. With within, each output becomes a series:
A value is null where the study hasn't warmed up yet (for example, the first 13 bars of a 14-period RSI when the ticker has little history).
Many indicators at once
POST /api/v2/technicals/technical/bulk computes a set of indicators over the same tickers and timeframe in one request, from one fetch of price history. Name each result with a key:
Each ticker's indicators map holds one entry per key (a key defaults to the indicator's name, so two sma entries need their own keys). Single-line indicators name their output line. If a requested indicator can't be computed for your plan, it's listed under excluded with the reason, and the rest are still returned.
Indicators and scans together
The same studies are scan filters, so the two endpoints divide the work:
- Scan to find the stocks that meet a condition across the whole market (for example, RSI(14) below 30).
- Compute indicators for the matches to rank or explain them (the exact RSI, distance from the 200-day average, ATR for position sizing).
One scan plus one bulk call covers any number of matches, which is far cheaper than computing indicators for every stock and filtering them yourself.
The names differ between the two
Scan payloads use the catalog's spelling: "Technical": {"RSI": [{"Params": {"Period": {"Value": 14}}}]}, with capitalized names and {"Value": n} wrappers. The technicals endpoints use lower-case slugs and plain numbers: /momentum/rsi with {"params": {"period": 14}}. Output names differ too: RSI in a scan's Want, rsi here; Signal there, macdsignal here.
The indicator list
Every endpoint, with its parameters, defaults and outputs, is under Technical Indicators in the API Reference.