1. Home
  2. Categories
  3. Test
  4. Clarification Required – SmartAPI NIFTY ONE_MINUTE Historical Data After CAS

Clarification Required – SmartAPI NIFTY ONE_MINUTE Historical Data After CAS

Test
Log in to reply
  • H

    We understand the CAS mechanism and timings. Our query is specifically regarding the behaviour of the SmartAPI Historical Candle API after CAS implementation, which is not clarified in the shared document.

    We are using:

    Exchange: NSE
    Symbol Token: 99926000 (NIFTY)
    Interval: ONE_MINUTE
    Request Window: 09:15–15:30 IST

    We tested five separate dates:

    4-Sep-2026
    7-Sep-2026
    8-Sep-2026
    9-Sep-2026
    10-Sep-2026

    For every date SmartAPI returns exactly 361 candles instead of 375.

    More importantly, the pattern is consistent:

    4-Sep and 9-Sep:
    09:15–15:14 continuously + 15:28 only
    Missing: 15:15–15:27 and 15:29

    7-Sep, 8-Sep and 10-Sep:
    09:15–15:14 continuously + 15:29 only
    Missing: 15:15–15:28

    Therefore, our question is not about CAS timings.

    We specifically need the SmartAPI Historical Market Data team to confirm:

    1. Is 361 candles the EXPECTED complete response for NIFTY ONE_MINUTE historical data after CAS implementation?

    2. Does SmartAPI intentionally omit the NIFTY minute candles between 15:15 and the final CAS timestamp?

    3. What does the final 15:28 or 15:29 historical candle represent? Is this the final actual NIFTY index value, CAS value, indicative closing value, or something else?

    4. Why does the final timestamp vary between 15:28 and 15:29 on different dates?

    5. Most importantly: should we treat these 361-candle responses as COMPLETE historical data, or is this a historical-data API issue?

    We do not want to interpolate or manufacture the missing candles. We need confirmation of the SmartAPI historical candle endpoint behaviour before using these dates in our system.

    Could you please forward this specific query to the SmartAPI Historical Market Data/API backend team and confirm the expected historical candle format?

    A simple confirmation of either:

    “361 candles / missing CAS-period minute candles is expected SmartAPI behaviour”

    or

    “SmartAPI should return those minute candles and this is a data issue”

    would allow us to proceed correctly.

    Thanks and Regards,
    Hareesh

    0
  • A

    Hello
    I have a similar time frame API for NIFTY and for me I do observe candles after 3:15 but they show the same frozen value until the settlement value comes down.

    0