SEBI Algo Trading Rules for Retail Traders: What Changed From April 2026
Blog by Aliceblue News Desk
21 October 2026
10 minutes
You set up a simple bot on your broker’s API, tested it for weeks, and then one morning your orders stop going through. The reason is often not a bug in your code. Since 1 April 2026, SEBI’s algo trading rules apply to every stock broker in India, and retail traders now need to follow a few specific steps before their automated orders reach the exchange.
Quick Answer
SEBI’s retail algo trading framework became mandatory for all stock brokers from 1 April 2026. Algo orders must be routed through a SEBI-registered broker and tagged with an exchange-issued Algo ID. API users need a whitelisted static IP and daily two-factor login. If your strategy sends fewer than 10 orders per second, you generally do not need separate exchange registration.
Table of Contents
- What Are the SEBI Algo Trading Rules for Retail Traders?
- How the SEBI Algo Trading Framework Works for Retail Traders
- What You Need to Set Up Before Trading
- Practical Example With Numbers
- Key Features of the New Rules
- Advantages for Retail Traders
- Risks and Limitations
- Tips for Beginners
- Old Setup vs New Setup
- Common Mistakes to Avoid
- Who Should Use Algo Trading?
- Conclusion
- FAQs
What Are the SEBI Algo Trading Rules for Retail Traders?
These rules tell retail investors how they can use automated trading in the Indian stock market. SEBI issued them through its circular dated 4 February 2025, called Safer Participation of Retail Investors in Algorithmic Trading.
Algo trading simply means letting a computer program place orders based on rules you set in advance. For example, buy 50 shares when the price crosses ₹1,500, or sell when the stock falls 2% below your buy price. The software watches the market and sends the order when the condition is met.
Before this framework, many retail traders connected scripts directly to broker APIs with little oversight. SEBI wanted every automated order to be traceable back to the person and strategy that sent it. The rules were delayed twice before becoming fully mandatory on 1 April 2026.
How the SEBI Algo Trading Framework Works for Retail Traders
Here is what happens when you run an algo under the new rules.
- You trade through a registered broker. You cannot connect your script directly to NSE or BSE. Your broker sits in the middle and is legally responsible for the algo activity on its platform.
- Your broker onboards the algo provider. If you use a third-party platform like Tradetron or Quantman, your broker checks and approves that provider before you can connect. Alice Blue has partnered with both platforms for this purpose.
- You register a static IP. A static IP is an internet address that stays the same. Your broker whitelists it, and orders from any other address are rejected.finseclaw+1
- You log in securely each day. API access uses two-factor authentication. Your session resets daily, so you need to log in again before the next trading day.
- Every algo order carries an Algo ID. This is a unique identifier the exchange assigns to your strategy. It lets the exchange trace any order back to the specific algo that generated it.
- The 10 orders per second rule determines registration. If your strategy sends fewer than 10 orders per second per exchange segment, you do not need to register it separately with the exchange. At or above that rate, registration through your broker is required.
- Records are kept for years. Order data is preserved so the exchange and broker can trace activity if needed.
What You Need to Set Up Before Trading
Before your first algo order goes live, you need four things in place.
A static IP address. You can get one from your internet service provider, or use a cloud VPS, which is a virtual private server that gives you a fixed IP. Many traders use a VPS because home internet connections can change IP addresses without warning.
A broker API key. Your broker issues this after you complete the required verification. Alice Blue’s API basics page explains how programmatic trading works on its platform.
A daily login routine. Because sessions reset every day, build the two-factor login into your morning routine before the market opens. If you skip it, your bot will sit idle all day.
A tested strategy. Backtest your logic on historical data before risking real money. Alice Blue’s guide on setting up your first algo system walks through this step.
Practical Example With Numbers
Say Priya in Bengaluru has ₹3,00,000 in her trading account. She writes a simple Python script that buys 100 shares of a large-cap stock when its price crosses a 20-day moving average.
Item | Before April 2026 | After April 2026 |
Order type | Market order | Limit order, or market order with protection value depending on broker |
Source of order | Any internet connection | Whitelisted static IP |
Login | Token could stay active for days | Fresh two-factor login daily |
Orders per second | About 1 | About 1 |
Exchange registration | None | None, since 1 is below 10 |
The stock trades at ₹1,500. Priya sets a limit buy at ₹1,502 for 100 shares, which is about ₹1,50,200 in value. She runs the script from her home connection on a static IP she registered with her broker.
One morning, her ISP resets her router and assigns a new IP. Her next order gets rejected because the new address is not whitelisted. She has to update the IP in her broker’s developer console before trading resumes. This is the most common practical problem traders face under the new rules.
A different trader running a scalping bot that fires 12 orders per second is above the threshold. That strategy needs formal registration with the exchange through the broker.
Key Features of the New Rules
- Algo ID tagging. Every algo order is traceable to the strategy that sent it, which helps the exchange and broker investigate errors quickly.
- Broker as principal. The broker is legally responsible for monitoring API activity and handling grievances. Algo providers act as the broker’s agents.
- Static IP whitelisting. Orders from unregistered or changing IP addresses are blocked. This is a security measure as much as a compliance one.finseclaw+1
- 10 orders per second threshold. Measured per exchange and per segment. Below it, no separate registration is needed.
- Daily session reset. You cannot keep an API session active overnight. Two-factor login is required each trading day.
- Audit trail. Order records are preserved so activity can be traced if needed.
Advantages for Retail Traders
- The main thing you gain is that every order can be traced back to you and your strategy. If something goes wrong, the exchange and broker can find the source of the orders quickly, which makes error resolution faster.
- Limit orders protect you from bad fills in fast-moving markets. A market order in a volatile stock can execute far from the last traded price. A limit order caps what you pay, though it may not fill if the price moves away.
- Daily logout and two-factor login reduce the chance of someone misusing a forgotten active session on your account. Registered brokers also screen third-party providers before letting them connect, so you are less likely to hand your account to an unchecked tool.
Risks and Limitations
- Rejected orders are the most common practical problem. If your home internet changes IP overnight, your strategy may stop silently at 9:15 AM. A stop loss that never reaches the exchange can turn a small loss into a large one.
- Limit-only orders can also go unfilled. In a fast move, your buy at ₹1,502 may never execute while the price runs to ₹1,520. This is a trade-off you accept for better price control.
- Automation also removes the human check, which can be a problem if the strategy is weak. Traders often trust a backtest too much. Leverage in futures and options magnifies any coding error. Compliance rules protect the process, but they do not make a strategy profitable..
Tips for Beginners
- Check whether your broker has updated its API and ask exactly what it requires from you before you start.
- Get a fixed IP from your ISP or use a VPS. Do not rely on a home connection that changes addresses.
- Use limit orders with a sensible buffer from the last traded price.
- Test with small quantities for at least a week before scaling up.
- Keep your own order rate low and log every order your code sends.
- Do not run an algo you cannot explain in two sentences.
- If you use a third-party strategy marketplace, check that your broker has onboarded that provider first.
Old Setup vs New Setup
Parameter | Before 1 April 2026 | From 1 April 2026 |
API access | Often open, loosely controlled | API key plus whitelisted static IP |
Order identity | Mostly broker-level logs | Exchange-assigned Algo ID |
Market orders via API | Allowed in most cases | Allowed only with a non-zero market protection value, or blocked entirely depending on broker |
Login | Long-lived tokens common | Two-factor, daily logout |
High-frequency algos | Little oversight | Exchange registration at 10+ orders per second |
Responsibility | Mixed | Broker is the principal |
Common Mistakes to Avoid
- Ignoring the static IP. Orders get rejected. Register it before you go live, and update it if your ISP changes it.
- Sending market orders without checking broker rules. Some brokers block them entirely on the API; others require a protection value. Check your broker’s documentation first.
- Assuming every API user must register with the exchange. Below 10 orders per second, you generally do not need to.
- Buying a guaranteed return bot. Unregistered or unverified providers are a red flag. Use only providers your broker has onboarded.
- Skipping the daily login. Your script will stop. Build the login step into your morning routine.
- Running live without testing. Paper trade or use tiny quantities first.
Who Should Use Algo Trading?
It suits traders who already have a tested, rule-based strategy and are comfortable with basic coding or a broker-approved no-code platform. Swing and positional traders who want automated entries and exits often find it useful.
It is less suitable for complete beginners who are still learning price action and order types, and for anyone who cannot manage a static IP or daily login. Long-term investors using mutual fund SIPs rarely need algos at all. If you are unsure whether algo trading fits your style, Alice Blue’s comparison of algo vs manual trading is a good place to start.
Conclusion
The SEBI framework did not ban retail algo trading. It made it traceable and broker-controlled. Since 1 April 2026, you need a static IP, a daily two-factor login, an Algo ID on registered algos, and a broker that has onboarded your strategy provider. Registration with the exchange applies only to above 10 orders per second. Before you automate anything, check your broker’s current API requirements, set up your static IP, and test with small quantities. Good compliance protects the process, but it does not protect you from a poor strategy.
Frequently Asked Questions
Yes. It is allowed through SEBI-registered brokers under the February 2025 framework. It has applied to all brokers since 1 April 2026.
Only if it sends 10 or more orders per second per exchange segment. Below that, you do not need separate registration, but you still need a static IP and daily login.
It is an identifier the exchange assigns to a registered algo. It is attached to each order so the order can be traced back to the strategy.
Common causes are an unregistered or changed static IP, an expired daily login, or a market order that does not meet your broker’s requirements. Check your broker’s API documentation and update your IP if needed.
It depends on your broker. Some block plain market orders on API entirely; others allow them only with a non-zero market protection value. Check your broker’s specific rules before coding.
Yes. Brokers allow API access only through a whitelisted static IP, usually one or two addresses. You can get one from your ISP or use a cloud VPS.

Blog by Aliceblue News Desk



