🔊Stocks Developer Alerts 🔊

DNS Issues - Only for information • On rare occasions, users report to us that website is not opening. On investigation, we find that it happens when their internet provider has DNS issues. • DNS issues on an internet provider typically affects some websites & not all. So users get confused thinking their internet is fine. • It can any affect any website including major websites like google. But the fault lies with your internet provider Solution: • Switch your network to different internet provider. Example from AirTel to JIO. • Report this problem to your internet provider • They fix such issues within same day as users start reporting

IIFL XTS We have seen a change notice from IIFL to change the login flow with a deadline of March 1st week. Achieving this would be extremely difficult as there are other items being worked on. We strongly recommend shifting your accounts to IIFL ONT (Markets) API. System Updates: - Angel recommended changes for Cautionary warning on stocks - AliceBlue new api - a workaround for price formatting issue for which we are not receiving any response from aliceblue

**Angel One: Cautionary Scrips warning** As many of you might have seen in the past, Angel One had block certain stocks for trading on API. They have now given a solution for this warning as seen in below url. Our team will incorporate this change in this weekend's release. https://smartapi.angelbroking.com/smartapi/forum/topic/5421/new-update-trade-in-cautionary-scrips-via-smartapi

*BUGS/QUESTIONS - POSITION BOOK RESPONSE* 1. Realized PnL for a closed position should be equal to NET PnL (Currently showing Realized pnl = Day's PnL) 2. M2M is wrong for overnight open positions 3. PnL (Net PnL is not provided in position response). 4. Fields 'buyPrice' & 'sellPrice' are always zero 5. Which fields we should use for 'net-buy-price' & 'net-sell-price'? Simple words In position API response, give us all these columns that we see on AliceBlue's Trading Website. They should exactly match.

Policy & Pricing Changes Broker Communication: Due to regulatory changes, all communication with brokers related to technical issues must happen through users **Pricing Change: Due to high costs of development & support, we have decided to increase cost of following broker by 100/- rupees Brokers: Profitmart, Dhan & AliceBlue

Dear clients, Please note that Angel one issue needs a fix on broker's side. There's nothing we can do about it. So instead of repeatedly asking us, it is better if you get your broker to fix it.

Angel one api issues ongoing Speak to your broker to get it sorted

Once angel one resolves issues. It would be automatically fixed on our side In case it doesn't, just make your account non-live & then live again.

Angel one issue Login issues on going please report to your broker

OAuth based Login - Regulations - We have yet to receive updates from many mid size or small brokers related to the changes needed. - Please understand that it requires development & you should check with us if your broker is supported for new OAuth logins Note: If a broker stops Non-OAuth logins without giving enough time to develop, then it will result in service being stopped for that broker.

PROFITMART - New API Login Process It seems the broker has launched a new login OAuth based login process. However, there is not enough information available on their website on how this needs to be done. We have very few Profitmart customers. So if you use profitmart, please get in touch with us & their Support team to have our queries resolved. Note: Profitmart support maybe stopped if the broker disables OLD login without advanced warning. So this is critical.

Please give importance to this. Not checking previous & next totp results in a lot of TOTP errors and inconsistent system. The totp generated by client is done using his own phone/pc time. There is always a high chance totp errors due to clock sync issues, network latency & user delay (when he tries to enter the totp manually). To accommodate for all these factors, all leading brokers check against previous and next totp on the server side validation. I have even shared a wikipedia article which confirms this. I do see some totp errors on your totp verification, hence highly recommend using above procedure.

Unstable TOTP on Aliceblue We see validation errors many times even with correct totp key & have to retry again and again sometimes. TOTP Server side validation - We have seen many brokers make a mistake of not validating against previous & next 30 seconds TOTP - This is needed to avoid clock sync issues between your customers and your server. For example, sometimes client's phone or pc clock may be a few seconds forward or behind standard internet time. - We have seen at least 3 brokers correct their TOTP server side validation after we reported this. - So please check your totp validation code and makes sure it validates in following sequence: 1. Current 30 second totp 2. Next (future) 30 second totp - helps those clients whose phone time is just ahead of standard time 3. Previous (past) 30 second totp - helps those clients whose phone time is just behind of standard time This is a standard practice & you can see this in below wikipedia article.

Dhan - Random Login Issues These have been popping up every now & then since we automated. It has been more than 2 weeks since we have reported this to Dhan. But no response. Solution: 1. Switch to old platform which is "Access token" based manual login 2. Just email Dhan and have a meeting setup with them to address these.

AliceBlue API - Order placement (rare) issue Some users reporting on rare occasions orders are not being placed and we are getting no order id in response. Extremely Irresponsible Behavior: The released the API without even doing basic testing. (Position book missing many imp fields, orders placement unreliable) We have not seen such careless release even with the small brokers. Please stay on ALICE_API_IPV6 platform. Do NOT use the new ALICE_API_V2_IPV6 platform.

**Angel One - Minor issues** On rare occasions we are seeing timeout issues on Angel One. 1. If you see timeout errors, please report to Angel One Smart API team 2. Also push them to get IPv6 support.

Aliceblue new API PNL issues PNL values are incorrect as brokers position book response has zero values for fields needed for PNL calculation. We have reported it to the broker & they are working on it. Until then please do not use latest aliceblue platform.

Subject: API changes needed for algo regulation compliance Body: Hello API Team, Regarding the upcoming algo trading regulations: 1. Please send us relevant documentation for "changes needed in API". 2. Do you support IPv6 addresses for Static IP? Regards,