We are validating an offline/source-only research capture, not placing orders. We use historical `interval=5minute`, NSE cash EQ instruments and the NIFTY 50/NIFTY BANK index series. Only candles labelled 14:45, 14:50, 14:55, 15:00, 15:05 and 15:10 are admitted. The first application-success response is captured after 15:15 and by 15:30 IST; later downloads are diagnostics, never replacements. No credentials or account details are needed for these questions.
1. Does timestamp `15:10:00+05:30` for a `5minute` historical candle denote exactly the half-open interval `[15:10:00,15:15:00)`? Is that timestamp the start of the event interval for cash equities and indices? 2. Is a trade/event timestamped exactly `15:15:00` excluded from that candle and assigned to the 15:15-start interval (or excluded from continuous-session candles for CAS securities)? Please distinguish boundary inclusion from whether a subsequent interval is published. 3. At what point is the 15:10 candle considered complete in the historical endpoint? Is there a completion indicator or documented delay, and can a response obtained after 15:15 still contain a partial 15:10 candle? 4. Can its OHLCV values later be revised? If so, under what circumstances, and is there any finality/revision marker or deadline? Please distinguish late trade ingestion, correction, aggregation cleanup and corporate-action back-adjustment. 5. Are historical candles assigned using exchange event time or vendor receipt/processing time? How are delayed or out-of-order events assigned, including exactly-boundary events? 6. How are corporate-action adjustments handled for intraday historical OHLCV: splits, bonuses, dividends, rights, demergers/schemes and symbol/ISIN changes? Which dates and OHLC/volume fields are changed, at what effective time, and is an explicitly unadjusted published series available? Please also confirm price/volume units, scaling and the corresponding index-series semantics. A current specification is needed because older support statements differ by date/action. 7. Since NSE CAS begins at 15:15 for eligible cash securities, can any CAS order, execution or indicative value after 15:15 affect a historical candle labelled 15:10, including through back-labelling or later aggregation/correction? Your CAS support thread describes separation from continuous-session candles; please confirm the exact boundary and exception handling.
Please identify what is guaranteed by the current service versus typical observed behavior. An inability to guarantee any item is also useful; we will retain that limitation rather than infer a guarantee.
Hi Salim, Thank you for checking this. I am following up regarding Kite Connect support ticket #405795. The support ticket has generated a feedback/closure message, while the technical clarification requested in this forum thread is still pending. Could you please provide the promised update on the seven questions above? In particular, we need the current guaranteed service semantics for the 5-minute candle boundary at 15:15, candle completion/revision behaviour, event-time assignment, corporate-action adjustment basis, and whether post-15:15 CAS information can ever affect a candle labelled 15:10. If any of these points cannot be guaranteed by the current service, an explicit confirmation of that limitation would also be helpful. Thank you.
Thank you for checking this.
I am following up regarding Kite Connect support ticket #405795. The support ticket has generated a feedback/closure message, while the technical clarification requested in this forum thread is still pending.
Could you please provide the promised update on the seven questions above?
In particular, we need the current guaranteed service semantics for the 5-minute candle boundary at 15:15, candle completion/revision behaviour, event-time assignment, corporate-action adjustment basis, and whether post-15:15 CAS information can ever affect a candle labelled 15:10.
If any of these points cannot be guaranteed by the current service, an explicit confirmation of that limitation would also be helpful.
Thank you.