Historical Data¶

The Historical Data API provides time-series OHLCV (Open, High, Low, Close, Volume) data for instruments across various intervals. This is ideal for charting, analysis, and building trading strategies.

Two endpoints share the same candle contract, the same intervals and the same per-call limits: one for instruments that are still trading, and one for F&O contracts that have expired. They differ only in how an instrument is identified. The expired-contract endpoint is coming soon; its contract is documented below so you can build against it ahead of time.

Get Historical Data¶

Endpoint

GET /market/historical/{interval}

Path Parameters

Query Parameters

Example Request

curl --location 'https://api.indstocks.com/market/historical/1minute?scrip-codes=NSE_3045&start_time=1750055540000&end_time=1750141940000' \
--header 'Authorization: YOUR_ACCESS_TOKEN'

Response Format The response uses a success boolean. data is keyed by scrip code, and each scrip's candles is an array of objects.

{
  "success": true,
  "data": {
    "NSE_1594": {
      "candles": [
        { "ts": 1782877500, "o": 1007, "h": 1013.9, "l": 999.3, "c": 1000.4, "v": 2847163 },
        { "ts": 1782881100, "o": 1000.4, "h": 1002, "l": 996.7, "c": 999.6, "v": 1389042 }
      ]
    }
  }
}

Candle timestamps¶

ts is the time at which the candle opens. Each candle covers the half-open interval [ts, ts + interval) — its own opening time is included, the next candle's opening time is not.

Worked example, on 5minute:

The 09:20 candle opens on the first trade at or after 09:20:00 and closes on the last trade before 09:25:00. The rule is the same on every interval, and on both endpoints.

Get Expired Contract Candles¶

The same OHLCV candles, for F&O contracts whose expiry has already passed — Get Historical Data covers instruments that are still trading. Together the two endpoints will give a strategy the full price history of a contract, from listing through to expiry.

Contracts here are identified by trading_symbol, the identifier returned by Search Expired Contracts and Contracts for an Expired Expiry. Exchanges reuse numeric instrument tokens once a contract has expired, so trading_symbol is the stable way to address a contract that is no longer trading.

Endpoint

GET /market/historical/expired/{interval}

Path Parameters

Query Parameters

trading-symbols, start_time, end_time and segment are the complete query contract; your account is resolved from the access token.

Example Request

These calls will work once the endpoint is enabled. NSE derivatives, using the default segment:

curl --location 'https://api.indstocks.com/market/historical/expired/1minute?trading-symbols=NIFTY26AUG2523950CE&start_time=1787542200000&end_time=1787652000000' \
--header 'Authorization: YOUR_ACCESS_TOKEN'

BSE derivatives, with segment=BFO:

curl --location 'https://api.indstocks.com/market/historical/expired/1minute?trading-symbols=SENSEX26AUG2581000CE&segment=BFO&start_time=1787542200000&end_time=1787652000000' \
--header 'Authorization: YOUR_ACCESS_TOKEN'

Response Format Identical in shape to Get Historical Data — a success boolean, data keyed per instrument, each with an array of {ts, o, h, l, c, v} candle objects. The only difference is the key: trading_symbol rather than scrip code.

{
  "success": true,
  "data": {
    "NIFTY26AUG2523950CE": {
      "candles": [
        { "ts": 1787543100, "o": 374.1, "h": 395.15, "l": 374.1, "c": 390, "v": 19955 },
        { "ts": 1787543160, "o": 390, "h": 402.5, "l": 388.2, "c": 399.7, "v": 14320 }
      ]
    }
  }
}

The candle contract is identical to the live endpoint. ts is the candle's open time in epoch seconds and covers [ts, ts + interval) (see Candle timestamps), start_time and end_time are epoch milliseconds, intraday buckets are anchored to the 09:15 IST session open, and each interval carries the same per-call maximum range.

Supported Intervals & Maximum Time Range¶

These intervals and maximums apply to both Get Historical Data and Get Expired Contract Candles.

This is the ceiling on a single call, not the depth of history available. Reaching further back is a matter of making more calls — one per window, walking backwards — not of asking for a wider window.

The maximum applies to the window you request, not to the span you get back. On 1week and 1month the returned candles land on week and month boundaries, so a full one-year request comes back spanning slightly less than a year.

Paging by date range¶

To build a series longer than one window, issue one request per maximum-width window and walk backwards, stitching the results together.

Notes¶

• start_time/end_time query parameters are in IST and Unix epoch milliseconds; the ts field inside each returned candle is in Unix epoch seconds.
• Keep each request within the maximum range for the chosen interval. A wider window returns the maximum range's data rather than an error, so size each request to the limit in the table above and page by date range for longer histories.
• start_time must not be later than end_time, which returns 400 {"debug_info": "start_time must not be after end_time.", "message": "Bad request"}.
• If requesting multiple instruments, each one gets its own candles array under data — they are not merged into a single list.
• The two endpoints take different identifiers and different batch sizes: scrip-codes with a maximum of five for live instruments, trading-symbols with a maximum of fifty for expired contracts.
• Both endpoints return the same candle fields, ts, o, h, l, c and v. For open interest, use the Option Chain.

See Also¶

• Market Quotes — live snapshot instead of historical candles
• Instruments — look up the SECURITY_ID used to build scrip-codes
• Contracts & Expiries — find the trading_symbol of an expired contract
• Error Bucket — DataException for invalid interval/time-range parameters