@pravinbj Unable to see the attached image.

However, DIY would stand for 'Do It Yourself'

@chinkgutto If your code is on your local machine, you can check other ISPs like Jio Fiber too.

@vbhide by log in, do you mean to login to get a trade token? if so, please use - login by password api.

please find the documentation here - https://smartapi.angelone.in/docs/User

@sj-91 Check the Credentials once again for the new app created with ip.

@vinayaditya Earlier there was no limit. Ideally it should be allow, you can try and test.

@algo_trading_50
It should be as per SEBI rules. It says family can share a single IP.
Now I have to keep multiple phones to place orders for each family member 😤

@charlotteemma4 Context? What API you are trying to access?

@pkrawat1 Feature not yet available.

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.

@ssumit @admin
SEBI allows family static ip sharing. Even Kite mentions it.

What is allowed? Family members can share a static IP. But there is an important condition: those accounts should be operated through the same developer account structure. In the Kite Connect setup, one developer account can create multiple API keys. Each of those keys can be used for different family-related accounts while using the same static IP mapped to that developer account. Example structure One developer account can be used for: Your personal account Your mother’s account Your HUF account Each can have its own API key, while running through the same static IP setup.

@namit check https://smartapi.angelbroking.com/smartapi/forum/topic/5527/urgent-unable-to-generate-api-key-for-market-api-type-and-historic-api-type

@ashishramani Check https://smartapi.angelbroking.com/smartapi/forum/topic/5527/urgent-unable-to-generate-api-key-for-market-api-type-and-historic-api-type

Deploy you algo on AWS, they provide static ip address

@admin It works with trading API key. Trading api keys allows history and market data also now

@d321860 you can edit the secondary static IP from the dashboard.

@jayesh_sapkale The IP address from where the order API originates should be same as that of the IP added while making the API key. Or else, the above error will come.

@MAWJ104 Yes you can do that.

@sejpalsinh As mentioned earlier, create a new static IP from Networking page and attach the IP with your instance of droplet.