Team,

Some more info in addition to the above.

I trade commodities starting morning till 10.00 pm.

I get this error exclusively between 9.00am to 3.30pm when NSE/ BSE markets are open.

Post 3.30pm I stop getting this error.

Hence the theory there could be an issue with the code OR multiple requests are being send is completely ruled out.

This is definitely Server throttling issue caused due to same API endpoint getting multiple hits.

What is weird is, me getting this error despite sending the request within rate limit (sending single request at every 2sec interval).

Having Rate limit check at server makes no sense, for those users sending requests within limits are still getting this error.

Expecting a resolution soon.

Regards
Diljeet

Dear Team,

I have been getting this HTTP 403 response with the error message "Access denied due to exceeding access rate" on the getCandleData endpoint, even though the request is sent at 2sec interval.

Even the very first request to fetch historic candles throws error.

{"todate":"2026-07-27 14:05","exchange":"MCX","interval":"FIVE_MINUTE","symboltoken":"573618","fromdate":"2026-07-07 14:05"}
Jul 27, 2026 2:12:29 PM com.angelbroking.smartapi.smartstream.ticker.SmartStreamListenerEventManager processQueue
SEVERE: Rate limit exceeded

Documentattion says getCandleData API endpoint can have 3requests / sec as the rate limit whereas I 'm sending only one request at every 2sec interval.

Until a few days back this was working fine.

Kindly check at your end for any restrictions applied for the given clientId.

CLIENT ID - D62917933
Endpoint - /rest/secure/angelbroking/historical/v1/getCandleData

Kindly help in resolving this at the earliest as not able to take any trade because of this error.

Any help would be highly appreciated.

Regards
Diljeet

@umangbhatia Hi Umang,
I've been facing the same issue while trading commodities. Have been sending request to fetch candle data at every 5sec interval but even the very first request throws 403 Rate limit exceeded. Until a few days back it was working fine for me. Were you able to resolve this. Any help will be highly appreciated.