🔊Stocks Developer Alerts 🔊

Master-Child Changes We have deployed a patch to handle edge cases in order execution: Outage Protection: Orders placed during app downtime are now ignored upon restart. Latency Guard: Orders received >10 seconds late are dropped to prevent "lag trades." Date Validation: Strict check to ensure broker overnight reset failures don't trigger yesterday's orders.

Profitmart Issue RESOLVED Broker fixed it.

More fixes applied We have applied fixes to IPv6 related issues. What kind of issues happened? So keep an eye for these errors: 1. Unknown host error. Failure to connect to broker's server 2. IPv6 bind error. Failure to assign a static Ipv6 to your trading account

IPv6 Changes - Causing connectivity issues on rare occasions We have done a lot of fairly complex changes & we have observed that on it is not yet 100% stable. IPv6 support is extremely important for us to be able continue business in the near future. Effective immediately, we are putting a hold on all other development work & the focus would be to make IPv4 stable. We have already taken multiple preventive measures, but more work is needed.

https://stocksdeveloper.in/documentation/supported-brokers/kotak/ Latest setup instructions for Kotak Neo 👆🏻 Note: We have also added support for Bracket & Cover orders on Kotak Neo.

https://stocksdeveloper.in/documentation/supported-brokers/kotak/ Latest setup instructions for Kotak Neo 👆🏻 Note: We have also added support for Bracket & Cover orders on Kotak Neo.

DNS Issues - Incident Update What happened? Today, towards the end of equity market some of the Google cloud servers in multiple data centers including Mumbai were affected with DNS issues. One of our server got impacted due to this & we had to shift all customers to another server. Impact: - This resulted in an outage situation for "some users" on server 1 for around 15 to 20 mins. Action: - We shifted affected users to other server, things were back to normal. Users who are on brokers which require manual login had to re-login. The issue has been resolved by Google in the meantime. - While this was an external issue on Google’s end, we know how important stability is. We have used Google Cloud for 10 years without an incident like this, so we do not expect it to happen again. - However, we have updated our internal processes to ensure we can recover even faster if it does.

Profitmart Update As per one of the user, it may take a few days for Profitmart to fix their issue, as they are awaiting some sort of permission from the exchange for the APIs. The reason given is strange and does not make much sense. We strongly request you to speak to Profitmart & get a latest update on when APIs will be restored for trading.

DNS Issues We are seeing DNS issues which is affecting website name resolution. This affects all brokers. DNS servers are not withing our control. They are used for converting website name to ip address. Once dns provider resolves this issue, errors will go away.

Profitmart's servers are down Same problem that we saw yesterday. Please report to your broker. We don't have a direct contact.

Tonight's Release (Bug Fixes) 1. Square-off of positions with quantity beyond FREEZE LIMIT. - Recent lot size change fix was applied to TRADE SCREEN & MASTER-CHILD. But we missed SQUARE-OFF positions button. 2. Angel One - MTF orders were wrongly shown as INTRADAY in orderbook (fixed)

Profitmart's servers are down Please report to your broker. We don't have a direct contact.

🛡 Static IP Compliance: Tips to Reduce Risk 1. Use a Static IP: We support both IPv4 and IPv6, but IPv6 is strongly recommended if your broker supports it. 2. Watch the Video: 👆 Please follow the steps in the video above. 3. Pro Tip: Have multiple accounts? Start by setting up just 1 or 2 accounts first. If everything runs smoothly, you can set up the rest. If you observe any issues or have any queries, please report to us.

IMPORTANT - IPv6 Compatibility As soon as you find out whether your broker supports IPv6 or not. Immediately inform us. This is critical for us to continue the business. Note: Zerodha already supports IPv6, so you can skip this for Zerodha.

Master-Child Copy - IIFL Master account HIGH RISK issue 1. On one of our customer, we had observed an issue wherein IIFL MARKETS api showed some unknown orders in orderbook. 2. The customer was using this IIFL account as master & our system obviously copied these unknown orders into child accounts. Because these orders looked similar to other orders & there was no way to figure out that they were faulty. 3. These orders were visible on the API for some time & later disappeared. 4. On investigation with IIFL API team, we found that this was due to some glitch on the brokers side. This was confirmed by IIFL. 5. The team mentioned that they will apply a fix. 6. Unfortunately, the same customer has now seen this issue twice after the first incident resulting in losses. 7. Due the nature of the issue, it is hard to even convince the user as our logs show unknown orders visible for some time & then after some time they disappear from the orderbook. We just wanted to bring this to your notice. This is a major bug & can result in losses. Hence, we do NOT recommend using IIFL MARKETS account as a master account until we get a confirmation from the broker that the issue has been permanently fixed.

IMPORTANT - IPv6 Compatibility Please ask the following question to your stock broker's API team. Query: Does your API allow us to use IPv6 static IPs? (If not, please have IPv6 support added asap. Because getting reliable India based IPv4 static IPs is difficult.) It is very important that you get answer to this question from your broker. Note: Zerodha already supports IPv6, so you can skip this for Zerodha.

Broker changes - Monitor Portfolio Carefully We are expecting *some* brokers to make changes, hence you are strongly advised to monitor your portfolio carefully & report any issues.

Angel One SENSEX - Issues resolved As informed by users.

A friendly message to our users... - Whenever a broker blocks certain symbols due to their risk management rules, there is nothing we or any *API user* can do about it. - Only your broker has the access to modify the rules - Some symbols are blocked on API but allowed on their trading platform because (as per Angel One "they can show risk warning message on their platform but not on the API") To fix this, WE HAVE GO AND PURCHASE ANGEL ONE & BECOME THE OWNERS, which is not possible any time soon. 😊 Have a beautiful year end & wish you all a great 2026!!! 🎉🎉🎉