Hi,

In the Python SDK, when I qury for current LTP, I'm getting wrong data. The bank nifty ltp I'm getting is 43851.05 from 9:15AM 21st Aug 2023.

Getting the error
File "/anaconda3/lib/python3.9/site-packages/SmartApi/smartConnect.py", line 224, in generateSession
if loginResultObject['status']==True:
KeyError: 'status'
when I try to login using the Python SDK.

@admin
Any response? Why is the ltp not updating. I've stopped the code and restarted a few time, but still getting the same wrong quote.

@admin
I'm getting connection timeout errors from 13:11 19th Oct 2023.

'Connection to apiconnect.angelbroking.com timed out. (connect timeout=7)'

Please check.

@admin

It's been almost 3 hours since this issue started occurring. Half of the trading session is over. Please provide an update on:

1. What is causing the issue? Is it bandwidth? Server capacity?
2. When will the issue be resolved?
3. What steps are being taken to ensure these issues do not keep happening, since this is the second time in 2 weeks that it has happened?

@admin
We are all waiting for a response. At least acknowledge that the issue is present.

@admin Any updates on this? I've been facing this issue the entire day.

@admin
Please acknowledge that you are aware of this issue and working on it.

@sa No. Multiple issues with both the API and the website. I'm able to login through both now, but I'm facing issues with every other API call.

@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.

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.

Facing the same issue. I've already posted this on a separate thread and others have confirmed that they are facing this issue as well. As usual the admins from Angel One are completely ignoring all the posts. Have some shame @admin. You guys reply selectively when it suits you and the replies are just "brush offs" on genuine issues being raised. I'm astounded that a company runs like this. I think it's time to involve some direct contacts on the escalation chain listed on their website and also start tagging their X/Twitter handle.

Separate issue from the getCandleData/getOrderBook rate-limit thread (topic 5639) — this is the static scrip master file itself, unauthenticated, no API key involved.

Endpoint: GET https://margincalculator.angelbroking.com/OpenAPI_File/files/OpenAPIScripMaster.json (~37MB, Content-Length: 36952921 confirmed via HEAD)

Production symptom (Python, urllib.request.urlopen().read()): three consecutive attempts between 09:15 and 09:44 IST today all failed with http.client.IncompleteRead — the server closed the connection before delivering the promised Content-Length, with successively less data delivered each time:

• 09:15:04 — 648,242 bytes read, 36,304,679 more expected
• 09:36:31 — 572,061 bytes read, 36,380,860 more expected
• 09:43:37 — 393,216 bytes read, 36,559,705 more expected

Independently reproduced from a completely different network (not the machine the above ran on) using plain curl, tested over both IPv6 and IPv4-forced, same URL:

• 60s attempt: 4.25MB delivered, ~71KB/s
• 60s attempt (IPv4 forced): 2.93MB delivered, ~49KB/s
• 180s attempt: connection closed by the server at 3.5MB (~48KB/s) — well short of 37MB even at that slow rate
• Retested ~90 minutes later: 336KB in 60s, ~5.5KB/s — getting worse, not better
• Baseline sanity check on the same network in the same window: an unrelated 10MB file from a different host downloaded at 3.1MB/s, ruling out a local bandwidth problem on our end

So this isn't one flaky client or one flaky network — two different tools (Python urllib, curl), two different networks, and both IP protocols all show the same severe throttling against this one host, persisting for over an hour and trending worse.

This is a hard blocker — the scrip master is a prerequisite before any strategy can even start routing, so trading has been unable to start today because of this alone.

Anyone else seeing this on margincalculator.angelbroking.com today? Given the pattern of the last several days on the rate-limit thread above, I'd appreciate someone actually looking at server-side telemetry/CDN health for this endpoint rather than the usual silence.

@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.

@admin Tagging you directly for visibility — six independent reports of this exact symptom, across two different endpoints, all well under documented limits, deserves more than the one dismissive reply on topic 5595. Could someone actually look at the server-side rate-limit telemetry for the accounts involved (linked above) and confirm whether this is a known issue?

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.

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.

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.

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.