India · SEBI algo trading rules

Static IP for algo trading, ready for SEBI's API rules

SEBI's February 4, 2025 circular requires API orders to come from a static IP registered with your broker, with full compliance from April 1, 2026. Fixedmark gives a bot running on any cloud, VPS, or laptop a dedicated IPv4 pair in Mumbai that you register as your primary and secondary IP, from ₹399 per month.

Join early access See pricing in ₹Early access

This page is general technical information, not legal, regulatory, or investment advice. Confirm your broker's current whitelisting rules before you register an IP, and check SEBI's latest circulars, because requirements can change.

What SEBI's circular requires

SEBI's circular on safer participation of retail investors in algorithmic trading, issued on February 4, 2025, sets the rules for retail API trading. In summary:

Brokers are responsible for every algo order that reaches the exchange through their API, including orders from a retail client's own code.
API access must be tied to the individual client, using client-specific API keys and a static IP address registered with the broker. Open, unauthenticated API access is not allowed.
Algos that send orders above an order-rate threshold set by the exchanges must be registered with the exchange, and their orders carry a unique algo ID.
Under the exchanges' implementation standards, a client registers one static IP and may add a backup. IP changes are limited to about once a week, and a static IP can be shared only between members of one family.
A September 30, 2025 SEBI circular extended the timeline, with full compliance from April 1, 2026. The static IP check is now live at the major Indian brokers.

For a retail trader, the practical result is simple. Your broker only accepts API orders from the IP address you registered, so your bot needs an address that never changes.

Why your cloud bot fails the check

A bot on Railway, Render, AWS Lambda, Vercel, or a home connection does not keep one public IP. Serverless functions leave from a pool of addresses that changes on every cold start. Containers get a new address when they redeploy or move hosts. Home broadband usually has a dynamic IP that changes when the router reconnects.

Each change means rejected orders until you update the IP with your broker, and changes are limited to about once a week. Shared IPs from a cloud NAT or a shared proxy plan are also a poor fit, because exchange rules only let clients share a static IP within one family.

Primary and secondary IPs map to your pair

Many brokers accept two addresses. Kotak Neo's API documentation lists a maximum of 2 IPs (primary and secondary), allows a change once every 7 days, and currently supports IPv4, with IPv6 described as coming soon. ICICI Direct lets you add a secondary IP address as a backup.

A Fixedmark pair fits this model. Register IP one as primary and IP two as secondary, and orders keep flowing if one proxy node is down. Fixedmark IPs do not rotate, so a registration that sits behind a 7-day change cooldown stays valid.

How Fixedmark helps

Fixedmark sits between your code and the broker API. Your bot sends its HTTPS requests through a proxy URL, and the broker always sees one of your two dedicated Mumbai addresses. Redeploy, change platforms, or scale out, and the registered IP stays the same.

Dedicated to you
Two IPv4 addresses that only your account uses. We never sell shared IPs for broker whitelisting.
Hosted in Mumbai
One short hop from Indian broker and exchange infrastructure, wherever your bot runs.
Primary and secondary
The pair fills both broker IP slots, so one node can fail without rejected orders.
Your keys stay private
TLS passes through end to end and is never decrypted. We cannot see your API keys, tokens, or orders.
Locked to your broker
Restrict your proxy token to your broker's API host, so a leaked token cannot reach anything else.
Connection logs
See the time, destination, and egress IP of every connection, which helps when a broker rejects an order.

Check your broker's rules

Each broker runs its own whitelisting flow. Before you register, check how many IPs it accepts, whether it accepts IPv6, how often you can change the IP, and which endpoints it checks. Common brokers with retail APIs include:

Zerodha Kite Connect
Upstox
Dhan
Angel One SmartAPI
Kotak Neo
ICICI Direct (Breeze API)

Set up a static IP for your trading bot

These steps work with any broker that whitelists by IP. Proxy URLs are issued at launch.

1
Create a Mumbai endpointChoose the India Trader plan. You get two dedicated IPv4 addresses in Mumbai and a proxy URL.
2
Register both IPs with your brokerIn your broker's API settings, add IP one as the primary IP and IP two as the secondary IP. If your broker accepts only one, register IP one and use the single-IP plan.
3
Store the proxy URL as a secretSet FIXEDMARK_PROXY_URL as an environment variable on the machine or platform that runs your bot. Never commit it to source control.
4
Route order requests through the proxyPass the proxy to your HTTP client, or set HTTPS_PROXY if your broker SDK is built on Python requests.
5
Verify the egress IPCall an IP echo service through the proxy and confirm the result matches what you registered. Then place a small test order during market hours.

# pip install requests  (urllib3 1.26+ for an https:// proxy URL)
import os
import requests

proxy = os.environ["FIXEDMARK_PROXY_URL"]
proxies = {"http": proxy, "https": proxy}

res = requests.get(
    "https://api.partner.example/v1/orders",
    proxies=proxies,
    headers={"Authorization": f"Bearer {os.environ['PARTNER_API_KEY']}"},
    timeout=15,
)
print(res.status_code, res.json())

# Python's requests library reads HTTPS_PROXY, so broker SDKs built on
# requests route through Fixedmark without code changes. Check yours.
export HTTPS_PROXY="$FIXEDMARK_PROXY_URL"
python bot.py

// npm install undici  (undici 8 needs Node.js 22.19+)
import { fetch, ProxyAgent } from "undici";

// FIXEDMARK_PROXY_URL=https://APP_ID:TOKEN@mum.egress.fixedmark.com:443
const proxy = new ProxyAgent(process.env.FIXEDMARK_PROXY_URL);

const res = await fetch("https://api.partner.example/v1/orders", {
  dispatcher: proxy,
  headers: { authorization: `Bearer ${process.env.PARTNER_API_KEY}` },
});
console.log(res.status, await res.json());

# Prints the IP the destination sees. Repeat it: each new connection
# leaves from one of the two IPs in your pair.
curl --proxy "$FIXEDMARK_PROXY_URL" https://fixedmark.com/api/ip

India Trader pricing

Planned launch pricing

Priced in rupees for Indian traders. Every option is a dedicated IPv4 address in Mumbai, with 50,000 requests and 5 GB of traffic per month, more than enough for order and quote calls.

1 dedicated IP
₹399/mo
- 1 dedicated IPv4
- IPv4, dedicated only
- Broker setup guides
Join early access
Dedicated IP pair
Recommended
₹749/mo
- 2 dedicated IPv4s for primary + secondary
- IPv4, dedicated only
- Broker setup guides
Join early access
Pair, billed yearly
₹6,999/yr
Saves ₹1,989 against monthly billing
- 2 dedicated IPv4s for primary + secondary
- IPv4, dedicated only
- Broker setup guides
Join early access

Planned launch pricing, subject to change before general availability. Planned payment in rupees through Razorpay with UPI, cards, and netbanking. Running a platform for many traders or a fintech app? See the developer plans.

Sources

Checked October 2026. Confirm current details on the vendor's site before you decide. Prices and limits change.

Frequently asked questions

Do I need a static IP for algo trading in India?

If you send orders through a broker API, yes. Under SEBI's February 4, 2025 circular, with full compliance from April 1, 2026, brokers accept API orders only from a static IP you have registered with them.

Can I use a shared static IP for broker whitelisting?

No. The exchanges' rules let clients share a static IP only within one family, so an IP shared with other proxy customers is the wrong fit. Fixedmark sells only dedicated IPs for this use case.

Why do I get two IPs?

Many brokers accept a primary and a secondary IP. Kotak Neo lists a maximum of 2, and ICICI Direct lets you add a secondary IP as a backup. Registering both keeps orders flowing if one proxy node is unavailable.

How much does a static IP for algo trading cost?

The planned India Trader plan costs ₹399 per month for one dedicated Mumbai IP, ₹749 per month for a dedicated pair, or ₹6,999 per year for the pair, which saves ₹1,989 against paying monthly. Pricing may change before launch.

Can I register the same IP with more than one broker?

Usually, yes. The IPs are dedicated to your account, so you can register them with each broker you trade through. Each broker's own rules on IP changes and limits still apply.

Does the proxy add latency to my orders?

Traffic takes one extra hop through Mumbai, close to Indian broker infrastructure. For bots running outside India, the added hop is usually small compared to the existing route to the broker.

Will my broker accept a Fixedmark IP?

Acceptance is your broker's decision. Check its API documentation or ask its support team before you register, and test with a small order first.

Related guides

Trade from a fixed address.

Join early access to get a dedicated Mumbai IP pair for your broker when Fixedmark launches.

Join early access Read the docs

Static IP for algo trading, ready for SEBI's API rules

What SEBI's circular requires

Why your cloud bot fails the check

Primary and secondary IPs map to your pair

How Fixedmark helps

Dedicated to you

Hosted in Mumbai

Primary and secondary

Your keys stay private

Locked to your broker

Connection logs