On this page
What the February 2025 circular says
The rule comes from one SEBI circular, SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2025/0000013, dated February 4, 2025, titled "Safer participation of retail investors in Algorithmic trading". It is addressed to stock exchanges and stock brokers, not to traders. Brokers carry the obligations, and they pass them on to you through their API terms.
The static IP requirement is one bullet in paragraph 5(I)(d). Brokers shall "not permit open APIs and allow access only through a unique vendor client specific API key and static IP whitelisted by the broker to ensure identification and traceability of the algo provider and the end user (i.e. investor)". The same paragraph requires OAuth-based authentication only, two-factor authentication for API access, and dealing only with empanelled algo providers. Here is the rest of the framework in short.
- The broker is the principal and any algo provider is its agent. The broker handles every complaint about API trading.
- Every algo order that flows through a broker's API is tagged with a unique identifier from the exchange, so each order has an audit trail.
- Algos written by "tech-savvy retail investors" must be registered with the exchange, through the broker, only if they cross an order-per-second threshold. A registered algo may be used for the investor's family, defined as self, spouse, dependent children, and dependent parents.
- Algo providers are not regulated by SEBI, but they must be empanelled with the exchanges. A provider of black box algos, where the logic is hidden from the user, must register as a Research Analyst.
The circular set no numbers, such as the threshold or how often an IP can change. Those come from the exchanges.
The exchange standards that set the numbers
NSE published the implementation standards as circular NSE/INVG/67858 on May 5, 2025. BSE published matching standards a day later as notice 20250506-3. Section A of the NSE annexure, "API Access Standards for Clients in Trading", is where the static IP rules live.
- To get API access, a client must give the broker a static IP address, which is mapped to the API keys the client connects with.
- The client may give one static IP (primary) and may add a secondary static IP "for the purpose of connectivity redundancy".
- A client may hold several API keys, for example per segment or per algo. Each key can map to the same primary and secondary IPs, or to its own pair. Unregistered algos must run through one predefined key.
- A client may update the mapped IPs "not more than once a calendar week". In extraordinary cases the client can ask the broker for an exception.
- A static IP maps to one client at a time. It can be shared only within one family, and the client must ask the broker in writing, by email from the registered address, or through a 2FA-validated request.
- All API sessions must be logged out every day before the next trading day starts.
NSE later added the detailed operational modalities in circular NSE/INVG/69255 on July 22, 2025. They repeat the static IP rule and describe how the broker tags orders, such as algo ID 99999 for an unregistered client algo. The broker sets these tags, not your code.
On April 30, 2026, NSE folded these rules into its consolidated circular NSE/INVG/73992 for non-NEAT front ends. Section 8.3 restates the static IP standards and the threshold in the same words, so the May 2025 numbers still stand.
Who needs a static IP, and whose IP it is
The static IP is not always yours. Standard A.5 of the NSE annexure assigns it by who built the algo, and NSE's retail algo FAQ narrows it further. It says a client static IP is required "only in case of Tech savvy Investor using API".
| How you trade | Whose IP is registered |
|---|---|
| Your own code calling the broker's API | Yours, the client's static IP |
| An empanelled algo provider using a vendor API key | The vendor's or the client's |
| A vendor platform hosted on the broker's servers | The broker's server IP (NSE FAQ, question 10) |
| An algo the broker built and offers | The broker's or the client's |
| Manual trading in the broker's web or mobile app | None. The static IP rule covers API access. |
The modalities also say that strategies from algo providers run on the broker's servers, and orders originate from there. For a tech-savvy client, the FAQ says the client hosts the algo "using a static IP at their end". The NSE documents above set no location rule for that machine. A VPS in Mumbai, a cloud VM abroad, or a box at home can all qualify, as long as orders leave from the registered address. Check your broker's terms, which can be stricter.
The 10 orders per second threshold
SEBI left the threshold to the brokers' Industry Standards Forum. The NSE standards set the Threshold Order Per Second (TOPS) at "not exceeding 10 orders per second" per exchange, applied "basis the calendar clock second of the broker server". The exchanges can change it after notice to the market.
- At or below 10 OPS, you do not register your algo. Your orders are still tagged as algo orders, with a generic ID the exchange provides.
- Above 10 OPS, you register the algo with each exchange it trades on. You send the details to the broker, the broker forwards them, and the exchange issues a registration ID that tags your orders.
- If you change the logic of a registered algo, you tell the broker, and the broker updates the registration with the exchange.
- The broker may set a lower limit per client. Orders above the limit are rejected or not processed.
The static IP rule does not depend on the threshold. A bot that sends one order a day needs a registered IP too. The threshold only decides whether you also register the algo.
Brokers enforce the limit in their API gateways. Zerodha's Kite Connect announcement set a strict 10 orders per second limit and returns HTTP 429 above it. Kotak Neo also rate limits its APIs to 10 orders per second. A loop that fires an order per instrument at the open can cross that without meaning to, so pace orders in your own code.
The timeline as it actually happened
The start date moved twice, and the final switch came in phases.
| Date | What happened |
|---|---|
| December 9, 2021 | SEBI discussion paper on algorithmic trading by retail investors |
| February 4, 2025 | SEBI circular issued. Standards due April 1, 2025, rules effective August 1, 2025 |
| April 1, 2025 | SEBI circular 2025/46 moves the standards to May 1, 2025. August 1 unchanged |
| May 5 and 6, 2025 | NSE (NSE/INVG/67858) and BSE (20250506-3) publish implementation standards |
| July 22, 2025 | NSE publishes detailed operational modalities (NSE/INVG/69255) |
| July 29, 2025 | SEBI moves the start date to October 1, 2025 |
| September 30, 2025 | SEBI circular 2025/132 sets a glide path. Brokers that are ready go live October 1 |
| October 31, 2025 | Milestone 1. Brokers apply to register their API algo product and at least one strategy |
| November 30, 2025 | Milestone 2. Those registrations complete |
| January 3, 2026 | Milestone 3. Each broker joins at least one exchange mock session |
| January 5, 2026 | Brokers that missed a milestone are barred from onboarding new retail API algo clients |
| April 1, 2026 | The framework applies to all stock brokers |
| April 30, 2026 | NSE consolidated circular NSE/INVG/73992 restates the standards |
The April 2025 circular and the September 2025 circular are both on SEBI's site. The September one also records the July 29 extension. A search of SEBI's circulars in November 2026 showed no further extension after April 1, 2026.
For traders, April 1, 2026 is the date that mattered. Zerodha, Kotak Neo, and Angel One all name it as the day API orders had to come from a registered static IP.
How the major brokers implemented it
Each broker turned the standards into its own console and API. The differences that matter are which endpoints are checked and whether IPv6 is accepted.
| Broker | IPs | Change limit | What is IP-checked | IP version |
|---|---|---|---|---|
| Zerodha Kite Connect | Primary, optional secondary | Once per calendar week | Order placement. Data, order book, and positions work from any IP | IPv4 or IPv6 |
| Upstox | Primary, optional secondary, must differ | Once per calendar week. Tokens are invalidated | Order traffic | IPv4 or IPv6 |
| Dhan | Primary and secondary | Once every 7 days | Orders, Super Order, Forever Order | IPv4 or IPv6 |
| Kotak Neo | 2 (primary and secondary) | Once every 7 days. New session needed | Place, modify, and cancel order APIs | IPv4 only for now |
| Angel One SmartAPI | Primary, optional secondary | Once per calendar week | Place, modify, and cancel order, and the GTT calls | IPv4 only for now |
Sources are Zerodha and its API FAQ, the Upstox static IP API, the DhanHQ authentication docs, Kotak Neo, and Angel One's notice and SmartAPI forum announcement. Per-broker setup steps are in the broker guides, such as Zerodha and Upstox.
"Once a calendar week" and "once every 7 days" differ. Under the first, two changes a few days apart can both pass if they fall in different calendar weeks. Under the second, you wait a full week. Plan any IP move as if you get one attempt.
Upstox rejects a request where both slots hold the same address, with error UDAPI1184. The primary and secondary slots are meant for two different addresses that fail over.
Some brokers also expose the registration as an API. Dhan has POST /v2/ip/setIP, PUT /v2/ip/modifyIP, and GET /v2/ip/getIP. Upstox has PUT /v2/user/ip with primary_ip and secondary_ip fields.
# Read the IPs Dhan has on file for you (primaryIP, secondaryIP, modify dates).
curl -s https://api.dhan.co/v2/ip/getIP \
-H "access-token: $DHAN_ACCESS_TOKEN" \
-H "Accept: application/json"
# Set both Upstox slots. This invalidates your current access tokens.
curl -s -X PUT https://api.upstox.com/v2/user/ip \
-H "Authorization: Bearer $UPSTOX_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"primary_ip": "203.0.113.10", "secondary_ip": "203.0.113.11"}'What changes in your trading code
For a bot that already logs in daily with an API key, the changes are one network rule and a few order rules.
- 1Find the IP your orders actually leave fromRun an IP echo from the machine or platform that sends orders, over IPv4 and IPv6 separately. If you host on serverless or a PaaS, the answer can change between runs. See why serverless egress IPs change.
- 2Match the IP version the broker acceptsIf your broker takes only IPv4 and your host prefers IPv6, the broker sees an address you never registered. Force IPv4 in your client. The IPv6 and IPv4-only allowlists post covers how.
- 3Register the primary, then the secondaryEnter the addresses in the broker console or its IP API. Double-check them first, because a typo costs you the week's change.
- 4Log in again from the registered IPKotak Neo requires a new session after an IP change, and Upstox invalidates existing tokens. Sessions are logged out daily anyway, so automate the morning OAuth and 2FA login.
- 5Route only order calls through the fixed IPAt Zerodha, Kotak Neo, and Dhan, only order endpoints are IP-checked. Quotes and WebSocket streams can keep their direct path, which keeps market data off your proxy's bandwidth.
- 6Pace orders and drop raw market ordersStay under 10 orders per second per exchange. The NSE modalities say algo orders must not reach the exchange as plain market orders, and bar IOC algo orders in the commodity segment. Zerodha now requires a market protection value on market orders, and Angel One's notice says market and IOC orders are prohibited for algo trading.
# The IPv4 and IPv6 addresses this machine uses for outbound calls.
curl -4 -s https://api.ipify.org; echo
curl -6 -s https://api6.ipify.org; echo # fails if you have no IPv6 routeHere is the routing split and pacing in Python with Zerodha's official kiteconnect client. Its constructor takes a proxies argument that it passes to the requests library. The order client uses a fixed-IP proxy, and the data client goes direct. Any proxy that leaves from your registered IP works the same way.
# pip install -U kiteconnect (needs a release with market_protection, such as 5.2.2)
import os
import threading
import time
from kiteconnect import KiteConnect
api_key = os.environ["KITE_API_KEY"]
access_token = os.environ["KITE_ACCESS_TOKEN"]
proxy = os.environ["FIXEDMARK_PROXY_URL"] # any proxy that exits from your registered IP
# Order calls leave from the registered static IP.
orders = KiteConnect(
api_key=api_key,
access_token=access_token,
proxies={"http": proxy, "https": proxy},
)
# Quotes, positions, and the order book can come from any IP at Zerodha.
data = KiteConnect(api_key=api_key, access_token=access_token)
class OrderPacer:
"""Allows at most `rate` orders in any rolling one-second window."""
def __init__(self, rate: int = 8):
self.rate = rate
self.sent: list[float] = []
self.lock = threading.Lock()
def wait(self) -> None:
with self.lock:
while True:
now = time.monotonic()
self.sent = [t for t in self.sent if now - t < 1.0]
if len(self.sent) < self.rate:
self.sent.append(now)
return
time.sleep(1.0 - (now - self.sent[0]))
pacer = OrderPacer(rate=8) # headroom under the 10 OPS limit
ltp = data.ltp(["NSE:INFY"])["NSE:INFY"]["last_price"]
pacer.wait()
order_id = orders.place_order(
variety=orders.VARIETY_REGULAR,
exchange=orders.EXCHANGE_NSE,
tradingsymbol="INFY",
transaction_type=orders.TRANSACTION_TYPE_BUY,
quantity=1,
product=orders.PRODUCT_CNC,
order_type=orders.ORDER_TYPE_MARKET,
market_protection=-1, # -1 lets the system apply its default protection
)
print("placed", order_id, "near", ltp)A rolling window of 8 is stricter than the exchange's calendar-second count, so clock skew between your server and the broker's cannot push you over. A Kite Connect forum reply says the limit applies per client ID, not per app, so share one pacer across every process that trades your account.
Users on the same forum report that a market order with protection can come back as a LIMIT order, so read the order type from the order book. If orders start failing with IP errors, the IP not whitelisted troubleshooting guide walks through the usual causes. For per-library proxy setup beyond Python, see selective proxying and per-client agents.
Choosing where the static IP comes from
You need an address that is stable and used only by you or your family. Three sources fit. One is a static IP on a business broadband plan. Another is a VPS or cloud VM with a reserved IP. The third is a dedicated static IP proxy, for a bot whose host IP changes, such as one on Lambda, Railway, or a laptop.
Rule out anything shared with strangers, such as a cloud NAT pool, a shared proxy plan, or a CGNAT home connection. Standard A.7 maps an IP to one client at a time outside a family. The tradeoffs in INR are in home static IP vs VPS vs proxy, and serverless specifics are in algo trading on serverless.
Doing this with Fixedmark
Fixedmark is in early access. It gives a bot running anywhere a dedicated pair of IPv4 addresses in Mumbai, reached through one proxy URL. You register the two addresses as your primary and secondary IP. Each new connection can leave from either address, so register both. See planned India pricing. Prices may change before launch.
Set the proxy URL as FIXEDMARK_PROXY_URL and pass it only to your order client, as in the code above. Then confirm the exit address with curl --proxy "$FIXEDMARK_PROXY_URL" https://fixedmark.com/api/ip, as the egress IP check describes. TLS passes through end to end, so Fixedmark never sees your API key, access token, or orders. Do not register the IPs from the trial or Starter, because both run on a shared pair.
Kotak Neo needs the session created from the IP that sends the orders, and each new connection through the pair can leave from either IP. Ask Fixedmark support before you rely on the pair with Kotak Neo. The Kotak Neo guide has the console steps.
Sources
Checked November 2026. Confirm current details on the vendor's site before you decide. Prices and limits change.
- SEBI: Safer participation of retail investors in Algorithmic trading (February 4, 2025)
- SEBI: Extension of timeline for formulation of implementation standards (April 1, 2025)
- SEBI: Extension of timeline for implementation, with glide path (September 30, 2025)
- NSE circular NSE/INVG/67858: implementation standards (May 5, 2025)
- NSE circular NSE/INVG/69255: detailed operational modalities (July 22, 2025)
- NSE: FAQ on safer participation of retail investors in algo trading
- NSE circular NSE/INVG/73992: consolidated NNF circular (April 30, 2026)
- BSE notice 20250506-3: implementation standards (May 6, 2025)
- Zerodha support: static IP for Kite Connect
- Kite Connect forum: preparing to comply with SEBI's retail algo rules
- Kotak Neo: static IP details for the Trade API
- Zerodha support: Kite Connect API FAQs
- Upstox developer docs: Update Static IPs API
- DhanHQ API v2 docs: authentication and static IP
- Angel One: what's changing in SmartAPI access from April 1, 2026
- SmartAPI forum: important updates to SmartAPI in compliance with SEBI guidelines
- GitHub: zerodha/pykiteconnect, the official Python client

