administrators

Hi Admin / Team,
​I am facing a persistent AB1021 ("Too many requests") error on the historical candle data endpoint for the NSE exchange, despite keeping my requests well within the documented limits.
​
Here are the technical details of the issue:

​Client ID: AACI752461
​API URL: https://apiconnect.angelone.in/rest/secure/angelbroking/historical/v1/getCandleData
​Error Message: {'message': 'Too many requests', 'errorcode': 'AB1021', 'status': False}

​Context & Anomalous Behavior:
​Request Frequency: My code is spaced out to send exactly 1 request every 5–6 seconds (~10–12 requests per minute). This is significantly lower than the documented 180 requests/min cap.

​Immediate Triggers: The error often hits on the very first NSE request of a batch, or almost immediately upon starting a low-frequency sustained scan.

​The MCX Comparison: Under the exact same script, identical network conditions, and the same public residential IP (no VPN), MCX commodity candle requests work perfectly all day without a single error. The restriction is uniquely triggering on the NSE endpoint.

​I initially raised support ticket #29145216 regarding this, but it was closed without a resolution. Could an admin or backend engineer please check the server-side rate-limit telemetry for my client ID (AACI752461)?

​Please verify if my actual measured rate is tripping an algorithmic false positive on the NSE historical data endpoint.

For last 15-20 days requesting subject matter but no answer.

I am told now "We request you to login to smartapi portal and share screenshot of API key dashboard where all apps are visible, so that we can check and update for the same.: but do not know how to do it, guide me please

@admin There is some issue at your end, using for more than 2 years, from may like he said no historical data update. Earlier 15sec/30sec/1min updata used to come, daily historic data used to update but now no.

@skammari I was facing similar issue with python sdk.

Looks like the gtt api path got prefixed with /gtt-service for /createRule, /modifyRule, /cancelRule which is not being allowed by the server and giving 404 with "no Route matched" error.
If possible, you can try calling with old paths for now until the fix it. It worked for me:

'api.gtt.create': ['/rest/secure/angelbroking/gtt/v1/createRule', '/gtt-service/rest/secure/angelbroking/gtt/v1/createRule'],

'api.gtt.modify': ['/rest/secure/angelbroking/gtt/v1/modifyRule', '/gtt-service/rest/secure/angelbroking/gtt/v1/modifyRule'], 'api.gtt.cancel': ['/rest/secure/angelbroking/gtt/v1/cancelRule', '/gtt-service/rest/secure/angelbroking/gtt/v1/cancelRule'],