@admin so annoying, every time this happens, I have to give an explanation to the clients.

Hi,

For enhanced security, we have updated our sign-up process where you're required to verify your mobile and email-id with separate OTPs.

Please note that you must use a unique email address each time you sign up.

For any queries, feel free to reach out at smartapi@angelbroking.com

Regards,
SmartAPI Team

Received this for my account today, does this impact the way we use SmartAPI?

Re: API down @admin I don't understand how can the API go down for 15 mins during market closing hours, this does not help at all in managing our positions.

@admin can you confirm what was the issue, I go very weird quantities back when fetching order book. Please confirm so our debugging becomes easier

{'variety': 'NORMAL', 'tradingsymbol': 'BANKNIFTY02FEB2342800CE', 'symboltoken': '49406', 'transactiontype': 'SELL', 'exchange': 'NFO', 'ordertype': 'MARKET', 'producttype': 'CARRYFORWARD', 'duration': 'DAY', 'price': '0.0', 'squareoff': '0.0', 'stoploss': '0.0', 'quantity': '44444444444444444444444444444444444444444444444444', 'trailingstoploss': '0.0', 'disclosedquantity': '0', 'triggerprice': '0.0'}},

The same issue with me, arbitrary output, even when passing the correct TOTP input to the program, sometimes it fails, sometimes it connects. Very unreliable.

@admin Hi, what is the update please?

Hi, I have been getting below errors throughout the day today.

requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='apiconnect.angelbroking.com', port=443): Read timed out.

Client Codes:
ADRV1036
BRBC1004
A655173
ADRV1039

Please can you have a look?

@admin so annoying, every time this happens, I have to give an explanation to the clients.

@admin Hi the issue only happened that day for start of day, it was resolved the same day.

@StocksDeveloper Happened the same with me, we rely on the Orderbook endpoint which did not return any response even when trades were being taken into account. Quite annoying as clients complaint and don't understand these issues.

Hi, I have had a very stable program running for the last 2 months except for a few instances when Angel One's server was down.

Today morning one of my systems logged in at 9:12 AM (which it does every morning) and the login was successful, it checks for the order book frequently from login time respecting the rate-limiting as well. On checking for the order book with this login session, it was returning as blank even when trades were being taken in account.

When I stopped that session and re-logged in via the APIs, the order book started showing up, can you please investigate and let me know why this happened for client code ADRV1039?

Yash