ProAlgoProAlgo
FeaturesBlog

Home › Blog › Regulation

Algo Trading Rules in India: What Retail Traders Should Know

Updated 18 Oct 2026·10 min read

Algo trading is legal for retail traders in India, but it is no longer a free-for-all. Since SEBI's framework became fully applicable on 1 April 2026, automated orders must be traceable, routed through your broker and sent from controlled access points. This guide explains the rules in plain language and what they mean for you.

The short version

Retail algo trading is allowed, through your broker's API. Every algo order carries an exchange-issued Algo-ID, API access is tied to a static IP, and your broker is responsible for what runs on your account. Light personal use below 10 orders per second does not need separate exchange registration of your strategy.

1. What counts as "algo trading"?

In simple terms, an algo order is any order generated and sent automatically by a program, with no human clicking "buy" or "sell" each time. A Python script on your broker's API, a bot that reacts to a TradingView alert, and a platform that places orders from rules you configured are all examples.

A basket order, or an order you place by hand from a web or mobile app, is not an algo order. A "price alert" that only notifies you is not one either.

2. How the rules arrived: a quick timeline

DateWhat happened
4 Feb 2025SEBI issued the circular on safer participation of retail investors in algorithmic trading.
5 May 2025NSE published technical implementation standards (static IP, API authentication, the 10 orders-per-second threshold).
22 Jul 2025NSE issued detailed operational modalities: empanelment, registration, testing and risk checks.
30 Sep 2025SEBI extended the deadline and set a phased glide path for brokers (Oct 2025 to Jan 2026 milestones).
5 Jan 2026Brokers that missed milestones were barred from onboarding new retail API algo clients.
1 Apr 2026The complete framework became applicable to all stock brokers.

3. Who is responsible for what?

4. The key rules, one by one

Algo-ID on every order

Every algo order must carry an exchange-issued identifier so that regulators can trace which strategy placed it. Registered strategies get their own ID. For small personal use below the threshold, your broker tags the orders with a generic ID, so you do not have to register anything yourself.

The 10 orders-per-second threshold

If your API activity stays under 10 orders per second per exchange or segment, it is treated as low-frequency retail use and does not need exchange registration of your own strategy. Above that, the strategy must be registered and approved. For context, a typical retail strategy that trades a few times a day is nowhere near this limit.

Static IP and API security

Your API key works only from an IP address registered with your broker. Authentication is stronger (for example two-factor login and session expiry), and sessions end daily, so a leaked key is far less useful to an attacker. Check how your broker handles this, because the IP that matters is the one the order actually leaves from.

Broker-side risk checks and kill switch

Brokers must run pre-trade risk checks (order size, price bands, exposure limits) and must be able to stop an algo quickly if it misbehaves. Expect rejected orders when your strategy breaks these limits. That is the system working as designed.

Selling strategies or signals

Strategies whose logic is disclosed ("white box") and strategies whose logic is hidden ("black box") are treated differently, and providers that sell or publish strategies generally have to register with SEBI, typically as a Research Analyst, in addition to exchange registration. If you pay someone for automated signals, check that they are properly registered.

5. What this means for different types of traders

You write your own code

Use your broker's official API, register your static IP, keep your order rate low and store keys safely. You normally do not need to register your strategy yourself.

You automate TradingView alerts

TradingView sends the alert, but a platform or script still has to place the order through a broker API. That second hop is where the rules apply: it needs a broker-approved setup and a registered IP. Ask your platform and broker how this is handled before going live.

You buy or subscribe to a strategy

Verify the provider's SEBI registration, ask which broker and exchange empanelment they use, and be wary of anyone promising fixed or "guaranteed" returns.

6. A practical checklist before you automate

  1. Confirm your broker offers a compliant retail API and ask about its algo policy.
  2. Register your static IP with the broker.
  3. Keep API keys secret and never share them in screenshots or chats.
  4. Set your own limits on top of the broker's: maximum loss per day, maximum position size, maximum orders.
  5. Paper-trade or run with minimal quantity first, and monitor the first live sessions.
  6. Keep a log of orders and changes to your strategy.
  7. Check the provider's registration if you use a third-party platform.

7. Common myths

"SEBI has banned algo trading for retail."

No. SEBI regulates it. The framework aims to make retail participation safer, not to remove it.

"I have to register every strategy I write."

Not for low-frequency personal use under the threshold. Registration applies at higher order rates and to providers offering strategies to others.

"A static IP makes my algo profitable or safe."

It only secures access. It says nothing about whether your strategy makes money. Most retail F&O traders lose money, so risk management matters far more than compliance.

"If my broker allows it, I do not need to care."

You are still accountable for your strategy and credentials. Understand what you are running.

"Algo trading guarantees profit."

It automates execution, not results. A bad strategy simply loses money faster and without hesitation. Backtests and live trading can differ a lot.

"Any free bot or script from social media is safe to use."

Unverified code can leak your API key, place unintended orders or break broker limits. Use only tools you understand, and prefer providers that work through your broker's official API.

"It is fine to share my API key with a signal provider."

Your credentials are personal and you stay accountable for activity on your account. Share access only through broker-approved methods, and never send keys over chat or email.

8. Sources and official references

Check the latest rules

Regulations and exchange circulars are updated often. This article is an educational summary, not legal advice, and details such as thresholds or procedures may change. Always confirm with your broker and the official SEBI and NSE websites.

Automate with risk controls built in

ProAlgo is a technology platform for multi-broker execution, TradingView webhooks, backtesting and a built-in risk engine.

See plans

Risk disclosure: Trading in securities, derivatives and commodities involves substantial risk and may result in loss of capital. Past performance does not guarantee future results. This content is for education only and is not investment advice or a recommendation to buy or sell.