@keshav-0 Multiple people are facing these issues and the admins here on this forum either do not exist or are completely unequipped to deal with anything other than giving vague useless replies. I have sent a detailed mail to support@angelone.in and escalation@angelone.in. If there is no satisfactory resolution, I'm planning to escalate directly to the CEO, Mr Ambarish Kenghe (ceoescalation@angelone.in) and post it all over social media like X/Twitter, tagging AngelOne's X handle. I suggest you and everybody facing issues use these channels as well to voice their issues since the administrators of this form have proved themselves completely incompetent.

I am trying to download the scripmaster in cache and even it is taking ages to complete. \scrip_master.py" 2026-08-21 10:30:04,820 INFO Another process is refreshing the scrip master; waiting up to 120s... 2026-08-21 10:32:05,590 INFO Ranged download from margincalculator.angelbroking.com: 37.0 MB in 1024 KB pieces... 2026-08-21 10:35:25,184 INFO scrip master: 8/37 MB 2026-08-21 10:41:18,303 INFO scrip master: 17/37 MB 2026-08-21 10:48:10,107 WARNING Ranged download failed from margincalculator.angelbroking.com: exceeded 900s budget at 21.0/37.0 MB 2026-08-21 10:48:10,579 INFO Ranged download from margincalculator.angelone.in: 37.0 MB in 1024 KB pieces... In my regular scripts which download them getting error Master download attempt 1 failed: ('Connection broken: IncompleteRead(140021 bytes read, 36812900 more expected)', IncompleteRead(140021 bytes read, 36812900 more expected)) 10:38:14 WARNING ORIG Master download attempt 2 failed: ('Connection broken: IncompleteRead(2407069 bytes read, 34545852 more expected)', IncompleteRead(2407069 bytes read, 34545852 more expected)) 10:40:02 WARNING ORIG Master download attempt 3 failed: ('Connection broken: IncompleteRead(6202101 bytes read, 30750820 more expected)', IncompleteRead(6202101 bytes read, 30750820 more expected))

@admin Come on Angel One. Show some professionalism. At least respond. Completely ignoring genuine issues is very unprofessional and reflects very poorly on the company culture and ethics.

@arunparida12 I am seeing the same issue on the official getCandleData endpoint. Environment: server-side PHP/WordPress Endpoint: /rest/secure/angelbroking/historical/v1/getCandleData Exchange: NSE Symbol token: 3045 (SBIN) Interval: ONE_DAY Range: approximately 90 days ending on the previous completed day The same authenticated session successfully returns HTTP 200 for login and HTTP 200 for /market/v1/quote, but the very first getCandleData request returns HTTP 403 with an empty/non-JSON response. No repeated requests or browser-side loop is being made. Could the SmartAPI team please confirm whether this is a server-side false rate-limit/access issue and check the endpoint telemetry? I can provide my Client ID privately to an admin, but will not post credentials or API keys publicly.

@krishnkant Yes, it was an issue from their backend but as of now i am completely able to to download the scrip data. i think the issue is now resolved from their end but it may take some time to reflect for some users. i suggest to try again after 30 to 45 minutes.

Same issue here — running a Nifty-options intraday bot polling getCandleData (FIVE_MINUTE) once every 5 minutes, ~0.003 req/s against the documented 3 req/s/client cap. Comparing the identical 09:15-10:35 window across three consecutive sessions: 12, then 17, then 27 rate-limit rejections, and the last two days both fully exhausted a 6-attempt retry budget on the very first request of the day, before any other call had been made. That makes six independent reports of this exact symptom now, across two different endpoints — candle data and order book — all well under documented limits: 5636/5637, 5611, 5625, 5595, 5560. I've put together a fuller writeup with the full data here: https://smartapi.angelbroking.com/smartapi/forum/topic/5639/getcandledata-rate-limit-false-positives-at-0-003-req-sec-six-independent-reports-zero-acknowledgment Would genuinely appreciate an actual look at the server-side telemetry rather than another "can't help with your code" response.

Yes, it was an issue from their backend but as of now i am completely able to to download the scrip data. i think the issue is now resolved from their end but it may take some time to reflect for some users. i suggest to try again after 30 to 45 minutes.

Multiple people are facing these issues and the admins here on this forum either do not exist or are completely unequipped to deal with anything other than giving vague useless replies. I have sent a detailed mail to support@angelone.in and escalation@angelone.in. If there is no satisfactory resolution, I'm planning to escalate directly to the CEO, Mr Ambarish Kenghe (ceoescalation@angelone.in) and post it all over social media like X/Twitter, tagging AngelOne's X handle. I suggest everybody facing issues use these channels as well to voice their issues since the administrators of this form have proved themselves completely incompetent.

Did you find any solution?

Same issue here — running a Nifty-options intraday bot polling getCandleData (FIVE_MINUTE) once every 5 minutes, ~0.003 req/s against the documented 3 req/s/client cap. Comparing the identical 09:15-10:35 window across three consecutive sessions: 12, then 17, then 27 rate-limit rejections, and the last two days both fully exhausted a 6-attempt retry budget on the very first request of the day, before any other call had been made. That makes six independent reports of this exact symptom now, across two different endpoints — candle data and order book — all well under documented limits: 5636/5637, 5611, 5625, 5595, 5560. I've put together a fuller writeup with the full data here: https://smartapi.angelbroking.com/smartapi/forum/topic/5639/getcandledata-rate-limit-false-positives-at-0-003-req-sec-six-independent-reports-zero-acknowledgment Would genuinely appreciate an actual look at the server-side telemetry rather than another "can't help with your code" response.

Hello, I have the same issue. My existing application: TradingView Auto Primary Static IP: 157.20.240.41 Current test results: generateSession() → SUCCESS getProfile() → SUCCESS getRMS() → AG8004 Invalid API Key getPosition() → AG8004 Invalid API Key searchScrip() → AG8004 Invalid API Key When I try to create a new Trading app using my server IP, the portal says that the Primary Static IP is already associated with another app. Could SmartAPI Admin please check whether my existing TradingView Auto application/API key is a legacy/orphaned app after the April 2026 portal migration? Please also check whether 157.20.240.xxx is still locked to an old/dead application and release/remap it if required. I want to continue with automated MCX trading using the SmartAPI Trading API. Please advise the exact backend action required. Thank you.