Screeners
Screeners run ready-made filters on a set of symbols and return the ones that meet the filter’s conditions.
| Endpoint | Method | Description |
|---|---|---|
| Configuration | GET | Lists every screener and the exact values each one accepts. Call it first. |
| Standard screeners | GET | Runs one of 111 screeners that you can customise: fields, universe, timeframe and sort. |
| Candlestick screeners | GET | Runs one of 23 fixed candlestick-pattern screeners. |
| Technical screeners | GET | Runs one of 6 fixed MACD, moving-average and MFI screeners. |
The order to follow
- Call Configuration and pick a screener.
- Read that screener’s entry to see what it accepts.
- Call the Standard, Candlestick or Technical API with the screener’s id.
Before you start
- You need your App ID and an access token (see the Authentication page of these docs). On every call, send them in the Authorization header as
APP_ID:ACCESS_TOKEN. - Every Screeners API is a GET call. Parameters go in the URL query string, for example
?screener_id=top_gainers&fields=t0_close_ltp. - Terms used on these pages: a screener is a ready-made filter; a universe is the set of symbols it scans (for example Nifty 50); a timeframe is the period over which a change is measured; a field is one column of the result.
Your first call, in three steps
- Call Configuration and note a screener id from
screeners_standard, for exampletop_gainers. - Call Standard screeners with
screener_id=top_gainers&fields=t0_close_ltp. - Read the result:
headernames the columns (symbolticker, thent0_close_ltp) and each array inbodyis one stock, in that order.
Last updated on