Client ID 1114883334, Data API plan active (validity 19 Dec 2026). /v2/charts/historical and /v2/charts/intraday work, but POST /v2/charts/rollingoption returns DH-905 “Missing required fields, bad values for parameters etc.” even with the exact example from your documentation: {“exchangeSegment”:”NSE_FNO”,”interval”:”1",”securityId”:13,”instrument”:”OPTIDX”,”expiryFlag”:”MONTH”,”expiryCode”:1,”strike”:”ATM”,”drvOptionType”:”CALL”,”requiredData”:[“open”,”high”,”low”,”close”,”volume”],”fromDate”:”2021-08-01",”toDate”:”2021-09-01"}. Same for WEEK, recent dates, SENSEX (BSE_FNO) and BANKNIFTY. Please enable or fix expired options data on my account.
Hi @prateekgupta2009 ,
You can now fetch up to 1 day of data per API request. To retrieve data for multiple days, iterate over the required date range and make a separate API request for each day, while adhering to the applicable rate limits.
My Data API plan is active (valid until 19 Dec 2026). Profile, historical/intraday index candles, option chain and intraday candles for live NSE_FNO options all work with my token. But POST rollingoption returns HTTP 400 DH-905 “Missing required fields, bad values for parameters etc.” for every request, including your documentation example:
{“exchangeSegment”:”NSE_FNO”,”interval”:”1",”securityId”:13,”instrument”:”OPTIDX”,”expiryFlag”:”MONTH”,”expiryCode”:1,”strike”:”ATM”,”drvOptionType”:”CALL”,”requiredData”:[“open”,”high”,”low”,”close”,”volume”],”fromDate”:”2021-08-01",”toDate”:”2021-08-30"}
I also tried expiryFlag WEEK, expiryCode 1/2, interval as number and text, securityId as number and text, BANKNIFTY (25) and SENSEX (51, BSE_FNO), recent ranges (Sep–Nov 2026) and short 3–5 day ranges. All return DH-905. Is expired options data enabled for my account, and what is the correct request?
Hi @prateekgupta2009 ,
Try fetching data for just 1 day per API request. For multiple days, make separate API requests for each day while adhering to the applicable rate limits.
Along with keeping fromDate and toDate within the single-day window, make sure securityId and interval are passed as strings (‘13’ and ‘1’) and that exchangeSegment is set to ‘NSE_FNO’ with instrument ‘OPTIDX’ matching the underlying index ID, as strict schema validation on v2/charts/rollingoption throws DH-905 on type mismatches.