List BSE and NSE stocks at their 52-week highs and lows in a single parameterless call

View all Indian Stock Exchange API endpoints →

Returns the stocks that are trading at their highest and lowest prices of the last 52 weeks on both the BSE and NSE. The endpoint takes no parameters. According to the endpoint documentation and its example response, the JSON object has two top-level keys, BSE_52WeekHighLow and NSE_52WeekHighLow. Each contains a high52Week array and a low52Week array. Entries in the high lists carry ticker, company, price and 52_week_high; entries in the low lists carry ticker, company, price and 52_week_low. In the example, tickers use the .BO suffix for BSE and the .NS suffix for NSE, and numeric fields are JSON numbers. The documentation warns that the response may be an empty list when the market is closed, so an empty result outside trading hours is expected rather than an error. No live probe call was recorded for this endpoint, so every field above comes from the documented example and has not been verified against a live response. The example also shows list lengths that differ between exchanges and sections, and no pagination or refresh interval is documented. The data is an informational snapshot, not a licensed tick feed.

API Features

BSE and NSE sets side by side The response is keyed by BSE_52WeekHighLow and NSE_52WeekHighLow, so both exchanges arrive in one payload and can be compared without a second request.
Separate 52-week high and low lists Each exchange block splits into high52Week and low52Week arrays, so breakout candidates and weakness candidates are already separated and need no client-side filtering.
No parameters to configure This is a plain GET with no query parameters, which makes it easy to run from a cron job, a spreadsheet import or an automation node.
Ticker, company, price and 52-week level Documented entries include ticker, company, price and either 52_week_high or 52_week_low, so a price can be compared with its 52-week level straight from the row.
Documented market-closed behaviour The endpoint documentation states that the list may be empty while the market is closed, which lets your code treat an empty array as an expected state and fall back to the last good list.

Live API Demo

GET /api/project/indian-stock-exchange-api/fetch-52-week-high-low-data

No parameters required. Click Query to call the API.

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/fetch-52-week-high-low-data?key=<API_KEY>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What does the 52 week high low endpoint return?

According to its documentation, a JSON object with BSE_52WeekHighLow and NSE_52WeekHighLow keys. Each holds a high52Week array and a low52Week array of stocks, and each entry lists the ticker, company name, price and the 52-week high or low value.

Does the endpoint need any parameters?

No. It is a GET request with no query parameters. The same call returns both exchanges and both directions (highs and lows).

Why did I get an empty list?

The endpoint documentation notes that the response may return an empty list when the market is closed. Schedule your calls inside Indian market hours, or cache the last non-empty response and serve it while the exchange is closed.

How do I tell BSE and NSE entries apart?

Use the top-level key, BSE_52WeekHighLow or NSE_52WeekHighLow. In the documented example, tickers also end in .BO for BSE and .NS for NSE.

Are these fields confirmed by a live test?

Not yet. No probe call was recorded for this endpoint, so the field names and sample values come from the endpoint documentation example. Parse defensively and check that a list exists before reading it.

Is price the same as the 52-week high or low?

Not necessarily. In the documented example, price and the 52_week_high or 52_week_low value are separate numbers and can differ slightly, so compare them rather than assuming they are equal.

How often is the data refreshed, and can I use it for execution?

No refresh interval is documented, so treat the response as a market snapshot and poll at a sensible rate. The data is informational and is not a licensed tick feed for order execution.

Related operations

Guides

View Subscription Plans →