@admin @administrators

I am facing similar error when using TradeTron. I am able to generate token but fails when placing order. No option to delete key and generate a new one. My client id is R56487580.

@arsm1057 what is the error that you are receiving?

This is essential feature to have to ensure security from stolen API key as big amount of money is involved.

Also, there should be separate API key each app. Currently it is single across multiple app.

Solved,

Just change the order type to Limit from market. Apparently market orders are not working for Margins as well.

@etiorz Try emailing smartapi@angelone.in. Currently deletion is not allowed.

@admin can you please look into this?
optionGreek returning AB9019 even during market hours.
Trading API key. Please check my account.

@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

@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.

@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