@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

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

@asgk1030 Read here.

@naveenkamaraj79

The redirect URL is available for the old API keys only.

Going forward, the API product will be used by tech savvy users only, and we request the users to use 2FA using login by password API for the same.

@Preetham you can place market orders in SmartAPI. They will be converted to Limit orders before sending it to the exchanges by MPP.

But it is better that the user himself sends limit orders so that the algo can predict if the orders are going into pending state.

@algo_trading_50 In their latest circulars, exchanges have given an option for either OAuth or 2FA login.

@hemanthmarreddy Could be because most brokers do maintenance tasks during night hours.

@preetham If it's for this specific duration then it could be because of intermittent server outage.

Master Scrip updates everyday ,refreshing tokens for older expiries to new ones.

So, if token 123456 is for SILVER FUTURES JAN2026, post its expiry 123456 is allotted to its next expiry which is SILVER FUTURES FEB2026.

Hence, you are unable to retrieve historical data for older expiries.

@pandyavarun9 Read here.

@smohit94 Try emailing - smartapi@angelbroking.com. If issue doesn't get resolved, try emailing - compliance@angelbroking.com.

@richaty You can sign up again with the with same phone and email id by putting in new client ID

@stander When creating your app, you can enter your current dynamic IP found via a "What is my IP" search to satisfy the mandatory field.