📢 [Important Update] Static IP Requirement for API Order Placement (Effective Soon)

Developer API
1

Dear Traders & Developers,

As per the upcoming regulatory guidelines, all orders placed via APIs will be required to originate from a registered Static IP address. Once the circular is implemented, this will become a compliance requirement, and any API order requests not originating from the registered Static IP will be rejected.

This post will help you understand what a Static IP is, how it differs from a Dynamic IP, and how you can obtain one in advance to avoid disruption once the rule takes effect.

What is a Static IP?

A Static IP is a fixed, unchanging IP address assigned to your internet connection or server. Unlike a Dynamic IP, which can change frequently, a Static IP remains the same — making it essential for secure, consistent, and authorized API integrations.

:pushpin: Please Note: The Static IP requirement applies only to APIs that involve order execution — specifically:

  • Placing an order
  • Modifying an order
  • Cancelling an order

All other APIs (such as fetching holdings, positions, funds, charts, etc.) will continue to function without any Static IP restriction.

Static IP vs Dynamic IP — What’s the Difference?

Most users are assigned Dynamic IPs by default — these IPs change frequently (e.g., after a reboot or reconnection). They are fine for general internet usage like browsing or email but are not suitable for secure API operations that require consistency and whitelisting.

In contrast, a Static IP remains constant and is manually assigned by your ISP or cloud provider. It’s ideal for secure trading applications because you can register it once and rely on it for all API order flows.

A Static IP usually comes at an additional cost, but it offers better traceability, security, and compliance with regulatory standards.

Example:

  • If your internet connection uses a dynamic IP, your address today could be 49.37.189.45, and tomorrow it might change to 49.38.201.78.
  • But if you opt for a static IP like 103.245.87.112, that value will never change unless you reconfigure or cancel the plan.

:magnifying_glass_tilted_left: Note: By default, most internet connections in India (home or mobile data) come with a Dynamic IP. You will only get a Static IP if you explicitly request it from your ISP or configure it in a cloud hosting environment.

How to Get a Static IP

:laptop: 1. Broadband or Fiber Internet Users (Home/Office)

If you’re using a home or office internet connection:

  • Contact your ISP (e.g., Airtel, Jio, ACT, Spectra, BSNL)
  • Request a Static IP Plan (usually costs ₹200–₹1000/month)
  • Once activated, the same public IP will be assigned to your router

:shield: Ideal for retail traders using desktop setups

:cloud: 2. Cloud Hosting Services (Recommended for Developers)

If you’re a developer or team running backend services, cloud hosting is a flexible and reliable option:

AWS EC2 – Use Elastic IP
:backhand_index_pointing_right: AWS Docs – Elastic IP

Google Cloud VM – Use Reserved Static External IP
:backhand_index_pointing_right: Google Docs – Reserve Static IP

Microsoft Azure VM – Use Reserved Public IP
:backhand_index_pointing_right: Azure Docs – Public IP

DigitalOcean Droplets – Use Floating IP
:backhand_index_pointing_right: DigitalOcean Docs – Floating IPs

You can deploy a small VM instance and configure it as a proxy or microservice that routes all API order traffic through the registered static IP.

:mobile_phone_with_arrow: 3. VPN Services with Dedicated Static IP

Some VPN providers offer dedicated Static IPs as an add-on:

  • NordVPN (with Dedicated IP add-on)
  • PureVPN (Dedicated IP plans)
  • ProtonVPN (for teams)

:warning: Ensure that the VPN provider supports full outbound IP consistency, and that the static IP doesn’t change between sessions.

Support for Primary and Secondary Static IPs

To provide better flexibility and reliability, we will support two static IPs per API App:

  • Primary IP:
    The main IP address from which API order requests will be expected.
  • Secondary IP:
    An optional backup IP — used only if the primary is unreachable or under maintenance. This is especially useful for teams running active/passive failover or alternate cloud setups.

Note: Both IPs must be static and pre-registered in your API App settings. API orders from any other IPs will be rejected once enforcement goes live.

:warning: Important: A Static IP can only be used by one customer. Once registered and linked to an API App, the same Static IP cannot be reused or registered by any other customer.

:white_check_mark: Once you register your Static IP(s) in the API App settings, you do not need to pass the IP in any individual API call. The platform will automatically validate that the request is originating from one of your registered IPs. This applies to all endpoints that require IP verification.

What if You Change Your Static IP?

If you’ve changed your ISP, server, or static IP address:

  1. Login to your developer section
  2. Navigate to your API App settings
  3. Update the Static IP fields with the new IP address
  4. Save the changes
  5. Ensure your new setup is correctly routing traffic through the updated IP

Note: Orders will start being rejected once the rule is enforced, unless your new IP address is updated and traffic originates from it.*

If you’re using dynamic IP again by mistake, you must switch back to a valid Static IP for order placement.

Stay Tuned for More

This post is part of a broader implementation based on the upcoming regulatory circular. In the coming days, we will share more updates on:

  • Effective date for Static IP enforcement
  • Order rate limiting guidelines
  • Algo registration process and documentation

We recommend preparing your infrastructure early to ensure a seamless transition.

1 Like
2

Thanks for the update, Anyways we have time till Oct 01 25

3

SEBI had previously issued a circular on February 04, 2025, introducing measures for safer retail participation in algorithmic trading, with an original effective date of August 01, 2025. However, following representations from stock brokers and ISF participants seeking additional time for compliance, SEBI has decided to extend the implementation timeline to October 01, 2025 , to ensure a smooth transition without market disruption. Stock Exchanges are hereby directed to (i) notify their members/participants about this extension and disseminate the circular on their websites, (ii) implement necessary systems and procedures for compliance, and (iii) make required amendments to their Bye-laws, Rules, and Regulations accordingly.

Refer : https://www.sebi.gov.in/legal/circulars/jul-2025/extension-of-timeline-for-implementation-of-sebi-circular-sebi-ho-mirsd-mirsd-pod-p-cir-2025-0000013-dated-february-04-2025_95677.html

4

Thank you for the detailed post.

I had a question regarding the restriction that a Static IP can be linked to only one API app. In some setups, two independent users (say, partners or team members) may share the same cloud instance or server — each running their own API app or strategy stack — but operating from the same static IP.

In such cases, would this setup be blocked under the current enforcement model? Or is the restriction more of a platform-level safeguard rather than an exchange-mandated rule?

Would appreciate any clarification, as shared environments help optimize resources but this constraint could make that setup non-viable.

Also, will it be necessary to register a static IP to your APP if you are using it only for data retrieval and not for order placement because that would again require a new static IP if done in a shared environment.

Thanks!

5

@Pradeep_Jaiswar @MohitGolecha how many family members account can use the same static IP?

6

How to register the Ips, and what is the timeline of changing already registered ip address

7

We’ll be sharing more details on it shortly.

The revised date for the circular implementation is not 1st October, 2025.

On an added note: Deprecation of V2 Market Data Feed Websocket
We’ll be deprecating our v2 websockets tomorrow!

8

@MohitGolecha Could you please confirm if there’s any indication that the circular deadline might be pushed from October 1st, 2025?

Also, we really appreciate that Upstox has been among the first brokers to implement the IP registration feature.

As a feature request, it would be very helpful if, along with the IP editing form, you could show either a “last updated” timestamp or a simple countdown or any other way your team can think to elevate the user experience and let users know when they’re next eligible to update their IP (since it’s restricted to once a week).

9

Eventually it will be scrapped. Or final circular will never be released :rofl: