Static IP for algo trading in India: rules, setup, cost

If you have searched for this, you have probably seen a warning from your broker that API orders from an unregistered IP address will be rejected. This guide explains where that rule comes from, what it actually requires, how to meet it at the two brokers Firefly supports in India, and why Firefly clients do not have to buy a static IP at all. Nothing here is investment advice; Fintrens is a software company, not a SEBI-registered adviser.

Why the rule exists

SEBI's 2025 framework for retail participation in algo trading, implemented through NSE and BSE circulars, allows automation only through the API of a SEBI-registered broker, and makes the broker responsible for every order that comes through it. One of the controls it asks brokers to enforce is that each API user's orders come from a fixed, pre-registered IP address. The point is traceability: an API key used from one known address is yours; a key used from many addresses, or many keys used from one address, looks like an unregistered portfolio manager running other people's money. The rule is aimed at that practice, not at individuals automating their own account. The broader framework — thresholds, algo IDs, white-box versus black-box — is covered in our SEBI algo trading rules guide.

What is actually required

Three things, all enforced by the broker. First, a static IP: an internet address that does not change, registered against your client ID. Second, one user, one IP, with brokers permitted to allow a second address per user for redundancy; the same IP cannot be registered for unrelated clients. Third, rejection, not warning: once a broker has switched the control on, an order sent from any other address is refused at the API with an error, and nothing reaches the exchange. Brokers rolled this out in phases through late 2025 and early 2026, and most now reject by default; if your broker still shows a grace-period notice, treat the deadline it names as real.

Two things are commonly confused with it. The orders-per-second threshold is separate: below it you do not need to register your strategy with the exchange, above it you do, and the static IP applies either way. And algo ID tagging applies to registered algos; a static IP is required whether or not your orders carry an algo ID.

How to get a static IP

Most home broadband connections in India hand out a different address every time the router reconnects, which is why the broker's error arrives after a power cut or a modem restart. The usual fixes are to ask your ISP for a static IP add-on, typically a few hundred rupees a month where offered; to run your trading program on a small cloud server, which has a fixed address by nature; or to use a trading platform that places orders from its own registered servers, which is the Firefly model described below. A consumer VPN does not work — its addresses rotate and are shared — and neither does dynamic DNS, which only maps a name to whatever address you currently have.

Registering at Zerodha

Log in to Kite, open your profile and look for the static IP section; enter the address and confirm with the OTP or TOTP prompt. Kite Connect then accepts orders only from that address for your client ID. If you run Firefly, the address you enter is the one we give you on the onboarding call. The rest of the Kite Connect setup — the Personal app, key and secret, daily token — is in the Zerodha algo trading guide and the Kite Connect setup page.

Registering at Angel One

Angel One asks for the IP when you create the SmartAPI app and lets you edit it from the SmartAPI profile afterwards. One address per app; changing it takes effect quickly but do it outside market hours so a live session is not cut mid-order. The full key setup, TOTP and permissions are in the Angel One algo trading guide and the SmartAPI setup page.

How Firefly handles it

Firefly places every order from Fintrens' own execution servers, which have fixed addresses. You register that address with your broker once, against your own client ID and your own trading-only API key, and from then on every order on your account comes from it. You keep custody, the broker still sees one user and one IP, and you do not need a static IP at home or a server of your own. If you ever stop using Firefly, you remove the address from your broker profile and the key stops working anywhere. This is also how the rule is meant to work: the address is tied to your account, not shared across accounts under one credential.

Common errors and what they mean

An "IP not whitelisted" or "request from unregistered IP" error on an order means the address the broker saw is not the one on file: your home address changed, or you are running from a new machine. A key that worked yesterday and fails today after a restart is almost always this. A login that succeeds while orders fail points to the same thing, because some brokers enforce the IP on order endpoints only. Fix the registration rather than retrying; repeated rejected orders can trip the broker's rate limits and lock the session for the day.

Questions people ask

Fintrens Technologies Pvt Ltd is not a SEBI-registered investment adviser or research analyst. This guide is general information, not advice; trading involves risk of loss.