# Historical API for MCX indices only returns 9:15–15:30 data, but KiteTicker streams till MCX close (23:30)

**URL:** https://tradingqna.com/t/historical-api-for-mcx-indices-only-returns-9-15-15-30-data-but-kiteticker-streams-till-mcx-close-23-30/195894
**Category:** Algos, strategies, code
**Created:** [July 13, 2026, 6:22am UTC](https://tradingqna.com/t/historical-api-for-mcx-indices-only-returns-9-15-15-30-data-but-kiteticker-streams-till-mcx-close-23-30/195894 "2026-07-13T06:22:00Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Sanghamitra\_R\_J](https://tradingqna.com/user_avatar/tradingqna.com/sanghamitra_r_j/32/92558_2.png) [@Sanghamitra\_R\_J](https://tradingqna.com/u/Sanghamitra_R_J)
#### Post date: [July 13, 2026, 6:22am UTC](https://tradingqna.com/t/historical-api-for-mcx-indices-only-returns-9-15-15-30-data-but-kiteticker-streams-till-mcx-close-23-30/195894/1 "2026-07-13T06:22:00Z")

</div>

There seems to be a mismatch between the historical candle API and live ticks for MCX indices.

- KiteTicker: We receive ticks for MCX indices from 09:00 to 23:30, which matches MCX market hours.
- Historical API: For the same MCX indices, candles/data are only available for 09:15 to 15:30, and the evening session data is missing.

Could you clarify whether this is expected behaviour, or if the historical API should also cover the full MCX session (09:00–23:30) for indices?

Thanks!

---

<div class="post-metadata">

### Author: ![Suny\_Banerjee](https://tradingqna.com/user_avatar/tradingqna.com/suny_banerjee/32/22338_2.png) [@Suny\_Banerjee](https://tradingqna.com/u/Suny_Banerjee)
#### Post date: [July 13, 2026, 11:45am UTC](https://tradingqna.com/t/historical-api-for-mcx-indices-only-returns-9-15-15-30-data-but-kiteticker-streams-till-mcx-close-23-30/195894/2 "2026-07-13T11:45:54Z")

</div>

> [@Sanghamitra\_R\_J](#):
>
> Historical API: For the same MCX indices, candles/data are only available for 09:15 to 15:30, and the evening session data is missing.

Hi @Sanghamitra_R_J , Thanks for flagging this — it’s already logged with our dev team. Since MCX chart data is connected to a few other parts of the system, we want to make sure the fix doesn’t affect anything else along the way. No fixed ETA yet, but it’s on our to-do list. Thanks for your patience!