Important Updates to SmartAPI in Compliance with SEBI Guidelines
-
@r345656 said in Important Updates to SmartAPI in Compliance with SEBI Guidelines:
Me, my son and my husband, all have individual angel broking account. I purchased static IP from my ISP and registered with my API. now if I do the same for my son or husband, I get error Primary Static IP is already associated with another app.
Those who leave in joint family or who do it from office using office IP, how we will use?
@admin Can you please guide on this?
-
Static IP cannot remain same always.
Many times internet line is down due to various reasons so ISP change its provider or we change from broadband to mobile or some other network.
In this case static IP can not remain same.In case of network failure we cannot switch to another network. It can cause trade loss during that period.
Since static ip we are not able to change location. We must stick to only one location. This is not fair.
Retail investors price of static ip and multiple static ip could be high.
If you dont want retail investors to survive then please let us know, we retail investors will try to do some other business.
-
@r345656 Host your trading bots on VPS that always have unique IP addresses.
-
@admin what if I am only using historical and live data apis and not routing orders thru api? Will this service like getltp and get candles continue as they are or do we still need static ips to even access api? Thanks.
-
@diwakarpant16 Static IP limitation is only applicable on order placement and modification APIs endpoints as per circular. "Trading API" app is under that umbrella.
-
@algo_trading_50
--so app created using trading API ---will not work if we do not have static IP .
M using it for historical data and getting feed over web socket , order placement are not integrated in the app . -
@archana Yes. For that reason we have "New Login" on https://smartapi.angelbroking.com.
-
@algo_trading_50 : But this one i doubt , it is still working ,web socket feed and historical data , all are working with trading API .
only issue is order placement . -
@archana Static IP limitation is only applicable on order placement and modification APIs endpoints as per circular, as mentioned above.
-
Dear SmartAPI Team,
I am writing this with serious concern regarding the current Static IP restriction policy.
At present:
- One SmartAPI profile = One trading account
- Each account requires a separate Primary/Secondary static IP
- Same IP cannot be reused for verified family accounts
This policy is creating unnecessary infrastructure complexity and cost, especially for families trading from the same system.
In direct comparison, Zerodha’s Kite Connect clearly allows:
- Multiple users under a single developer profile
- Single static IP registration
- Centralized API management
- Clean compliance structure
- Much lower operational cost
- Seamless scaling for family and multi-account traders
This makes Kite Connect significantly more practical for serious algo traders.
Right now, SmartAPI’s structure forces:
- Multiple Elastic IPs
- Multiple servers or routing setups
- Higher AWS cost
- Complicated infrastructure
- Unnecessary technical overhead
For family traders and serious API users, this becomes a strong reason to shift platforms.
To be very clear — if this policy continues, many multi-account users (including my entire family) will have no practical option except to migrate to Kite Connect, where infrastructure is simpler, scalable, and developer-friendly.
We genuinely appreciate SmartAPI’s service and want to continue here. However, infrastructure flexibility is not optional for algo traders — it is fundamental.
Kindly reconsider:
- Allowing multiple verified family accounts under one developer profile
OR - Allowing shared static IP approval for related accounts
This single change would significantly improve adoption and long-term retention.
I hope this feedback is taken seriously, as it directly impacts platform competitiveness in the API ecosystem.