@kp_rahul @admin gentle reminder — 4 days, no response yet. This is a compliance question and I'd rather get it right before onboarding users. Even a short pointer to the relevant clause in the SmartAPI terms would help.

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.

@admin when is the near future arriving ? when will we get support for ipv6?

In my case, after login succeeded, the very first call itself is failing with "Access denied because of exceeding access rate" error. This is happening for https://apiconnect.angelone.in/rest/secure/angelbroking/historical/v1/getCandleData API. Lately, the calls to this API is throwing the rate limit error most of the time for me, even though it is the only call made after login from my account. AngelOne SmartAPI Team - You have some serious issue here to fix. This is affecting lot of people. Your rate Limiting logic has major bugs to be fixed. One to fix this issue: You can cache the candle data, so that you don't need to build the response for every calls. This should drastically reduce your server over load.

@admin please give some update