Algo trading remains legal for retail investors in India. SEBI's framework, issued on 4 February 2025 and fully mandatory from 1 April 2026, regulates the plumbing rather than the activity: every algo order carries a unique Algo ID tied to a strategy registered by your broker with the exchange, API access comes from static IP addresses whitelisted in advance, and the broker is accountable for the algos it permits. You do not need SEBI registration to automate your own account. You do need a broker that has completed its side, and a fixed address to trade from.
01What the framework is
SEBI's circular SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2025/0000013, dated 4 February 2025, set out a framework for what it calls safer participation of retail investors in algorithmic trading. It was not a restriction on who may automate. It was an answer to a structural problem: retail algo order flow was reaching the exchange through broker APIs with no reliable way to attribute it to a specific strategy, and no clear line of responsibility when something misfired.
The fix is identification. If every automated order can be traced to a registered strategy and a known origin, the exchange can see what is happening in its own order book, and the broker who permitted it can be held to it. Almost every specific requirement in the framework follows from that single idea.
02How it arrived
The rollout was phased, and the phasing is why so much published commentary is now out of date.
| Date | What happened |
|---|---|
| 4 February 2025 | Circular issued, setting out the framework |
| 31 October 2025 | Brokers to have registered at least one retail algo product and strategy with the exchanges |
| 5 January 2026 | Brokers that had not complied barred from onboarding new retail API clients |
| 1 April 2026 | Full framework mandatory for all stockbrokers |
The original timeline was more aggressive and was extended, which produced two waves of commentary: one describing rules that were then postponed, and one describing a glide path that has since been completed. Anything written before April 2026 that tells you what will happen is describing a state of the world that has already passed.
03The four things it requires
Stripped of the compliance vocabulary, the framework asks for four things.
- A unique Algo ID on every algo order. Issued by the exchange for a registered strategy. It travels with the order, so automated flow is attributable rather than anonymous.
- Broker registration of the algo. Your broker registers retail algo products and strategies with the exchange. This is the broker's obligation, not yours, but it determines whether your broker can legally offer you API access at all.
- Static IP whitelisting. API access for algo trading comes from addresses registered in advance. A dynamic home connection does not qualify.
- Broker accountability. The broker is responsible for the algos it permits on its API, which is why brokers now ask far more detailed questions before enabling automated access.
04The order-rate threshold
Not every automated strategy is treated the same way. The framework separates them by order rate, with a threshold widely reported as 10 orders per second per client. Below it, a strategy is handled more lightly. At or above it, it falls into the category carrying exchange registration and tighter controls.
For most people reading this, the threshold is not close. A systematic options strategy that enters and exits a few positions a session places orders in single digits per day, not per second. The threshold exists to separate retail automation from high-frequency activity, and retail automation sits several orders of magnitude below the line.
Brokers differ in how they implement the threshold and what they ask you to declare. Treat the figure as the shape of the rule and confirm the current number and its application with your own broker before you build around it.
05What still needs no registration
This is where most confusion sits, so it is worth stating plainly. Automating your own account, with your own capital, through your own broker login does not make you a regulated entity.
SEBI registration attaches to what you do for other people. Advising them on securities makes you a Research Analyst or Investment Adviser. Managing their money makes you a Portfolio Manager. Selling them trade recommendations puts you in the same territory. Running code on your own account does none of that, and the algo framework did not change it.
Writing software is likewise not a regulated activity. A developer who builds a strategy to your specification and hands you the code is doing engineering work. The line is crossed when someone tells you what to trade, takes custody of your funds, or trades your account for you. We cover where that line sits in more detail in algo trading in India.
06What it changes in practice
For someone automating a strategy on their own capital, the framework has three practical consequences.
Where your code runs now matters. The static IP requirement is the requirement people underestimate. A laptop on home broadband was the default setup for years and it no longer clears the bar. The strategy needs to run somewhere with a fixed address, registered with the broker in advance. That is a small monthly cost and a one-time setup, but it has to be planned rather than discovered on the morning you intended to go live.
Your choice of broker narrowed. Brokers that did not complete their registrations were barred from onboarding new retail API clients from January 2026. Before committing to a broker for automation, confirm its API is open to new algo clients rather than assuming it.
Approval takes time. Because the broker carries responsibility for what runs on its API, enabling access now involves declarations about your strategy and its order behaviour. Build that into your timeline instead of treating it as a formality.
07Verify this against the source
Regulation is the one topic where you should not take a vendor's summary as final, including this one. This page is educational, it reflects the framework as we understand it in September 2026, and implementation details continue to be refined by the exchanges and by individual brokers.
Read the circular itself, SEBI's February 2025 circular on safer participation of retail investors in algorithmic trading, and ask your broker what it specifically requires of you. If you need to reach SEBI directly, we maintain a list of SEBI contacts for exactly that purpose.
08Questions people ask
Is algo trading legal in India?
Yes. Algorithmic trading is legal for retail investors in India and SEBI's 2025 framework did not ban it. The framework regulates how brokers offer algo access rather than prohibiting the activity. What changed is that every algo order must now be traceable to a registered strategy through a unique Algo ID, API access must come from whitelisted static IP addresses, and your broker carries formal responsibility for the algos it permits.
Do I need SEBI registration to run my own algo?
Not for trading your own capital through your own broker account. SEBI registration as a Research Analyst, Investment Adviser or Portfolio Manager is required for advising others, managing other people's money or selling trading recommendations. Running an automated strategy on your own account is none of those. What the framework does require is registration of the algo itself with the exchange, which is carried out by your broker rather than by you.
What is an Algo ID and who issues it?
An Algo ID is a unique identifier issued by the stock exchange for a registered algorithmic strategy. From 1 April 2026 every order generated by an algo must carry one, so that the exchange can attribute automated order flow to a specific registered strategy. Retail traders do not apply for it directly; the broker registers the algo with the exchange and the identifier is attached to the orders routed through it.
What is the order-per-second threshold in SEBI's algo framework?
The framework distinguishes algos by order rate, with a commonly cited threshold of 10 orders per second per client. Below that rate a strategy is treated more lightly; at or above it, the algo falls into the category requiring exchange registration and tighter controls. Most retail options strategies place a handful of orders per session and sit far below the threshold. Confirm the current figure and how your broker applies it with the broker directly, since implementation details differ between them.
Why does my broker need a static IP for API trading?
Static IP whitelisting lets the broker and exchange tie automated order flow to a known origin. From 1 April 2026 API access for algo trading is expected to come from IP addresses registered in advance with the broker. In practice this means a home broadband connection with a changing address is no longer sufficient, and the algo needs to run somewhere with a fixed address, such as a VPS, with the address registered before it can trade.
Can I still run my algo from my laptop at home?
Generally no, not for API-based algo trading, because access is expected from a static IP registered with your broker in advance and home broadband addresses usually change. The practical answer is a small VPS with a fixed address, registered before you go live.
Does hiring a developer to build my algo require registration?
No. Writing software to a specification is engineering, not a regulated securities activity. The regulated activities are advising on securities, managing someone else's money and dealing on their behalf. A developer who builds what you specify and hands it over does none of them.
QuantNifty is an algorithm development and consulting firm. We are not a SEBI-registered Research Analyst, Investment Adviser, Portfolio Manager or Broker. This page is educational, is not legal or investment advice, and is not a substitute for reading the circular or asking your broker. Regulation changes; verify anything you intend to rely on. Full risk disclosure is in our Terms.
Building something that has to clear all of this?
We write execution systems that run where they are supposed to run, with the risk plumbing the framework expects: broker-side stops, fill confirmation, order repricing and a kill switch.
Tell us what you want built