algo trading compliance 2026

As of July 2026, the SEBI algo trading rules for retail traders are set by SEBI's February 2025 circular on the safer participation of retail investors in algorithmic trading, which became fully mandatory for all Indian stockbrokers on 1 April 2026. In short: any automated order must run through a broker-approved API, be tagged with an exchange-issued Algo-ID, and — if you cross the order-per-second threshold (currently 10 orders per second per exchange) — your algo must be registered with the exchange through your broker. Below that threshold you can run a personal algo without registration. This checklist walks retail traders through every requirement. Rules can change, so always confirm the current position with your broker and SEBI. I am Jayadev Rana, a TradingView-certified Pine Script developer based in India, and I have spent 8+ years building automation for traders across 14+ countries. When the 2025 circular landed, I had to revisit almost every live client bridge I ran into Indian brokers. Below is the plain-English checklist I now walk clients through before we automate a single order. What actually changed under the 2026 SEBI framework The core document is SEBI Circular SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2025/0000013, issued on 4 February 2025. It does not ban retail algo trading — it formalises it. For the first time, retail participation through broker APIs is explicitly allowed, but inside a controlled perimeter where every automated order is traceable back to a client, an algo and an IP address. SEBI later extended full implementation to 1 April 2026 and gave brokers a “glide path” of milestones through late 2025 to get their systems registered and tested. The stock exchanges (NSE and BSE) publish the detailed implementation standards that spell out the operational rules: thresholds, tagging, registration and API security. Those exchange standards, not memory or old blog posts, are the document you should check for exact numbers. The retail algo compliance checklist Here is the checklist I use. Treat it as a starting map, not legal advice — the precise operational details sit in your broker's and exchange's current circulars. 1. Know your order-per-second (OPS) threshold The exchanges set a Threshold Order Per Second, currently not exceeding 10 orders per second per exchange or segment, per client. Stay below it and you are treated as a regular API user — no algo registration is needed for a personal strategy. Cross it and you are an algo trader in SEBI's eyes, with registration obligations. The exchanges can revise this number with prior notice, so check the latest figure with your broker rather than assuming. 2. Register any algo that crosses the threshold If your strategy will place orders faster than the threshold, it must be registered with each exchange where it runs — and that registration happens through your broker, not directly with SEBI. Your broker submits the details, the exchange issues a unique identifier, and any later change to the algo's logic needs re-approval. Plan for that lead time before go-live; you cannot flip a switch the night before. 3. Use only broker-approved, secured API access The era of freely-connecting “open APIs” is over. Under the framework, API access must use: OAuth-based authentication with mandatory two-factor authentication (2FA) on every session login; Unique API keys or credentials per client or algo provider — no shared keys; Static, whitelisted IP addresses — dynamic or rotating IPs are not accepted (immediate-family accounts may share a static IP with prior broker permission); Daily auto-logout and password or token expiry, as enforced by your broker. 4. Decide where your algo is hosted The framework expects retail algos to run on the broker's own empanelled systems. There is a carve-out for tech-savvy traders who self-host their strategy logic, but only from a registered static IP and taking full responsibility for it. If you use a broker-hosted no-code platform you generally do not need to supply your own static IP; if you run your own bridge on a VPS, you do. In practice you can usually update your mapped static IP no more than once a calendar week, so choose a stable host from day one. 5. Understand white box vs black box algos SEBI classifies strategies into two buckets: White box (execution) algos — the logic is transparent and replicable; standard exchange registration applies. Black box algos — the logic is hidden and cannot be reproduced by the user; the provider must be registered as a SEBI Research Analyst and keep a research report for each strategy. If you are buying a ready-made algo whose logic you cannot see, ask the vendor which bucket it falls in and whether they are registered accordingly. If they dodge the question, that is your answer. 6. Use only permitted order types From 1 April 2026, MARKET and IOC (Immediate-or-Cancel) order types are not allowed for algo execution on the exchanges. If your strategy fires market orders, switch it to LIMIT orders with a DAY validity before you go live, or your broker will reject them. This is an easy one to miss when you port an older TradingView strategy across. 7. Confirm every order is tagged with an Algo-ID From 1 April 2026, all algo orders — both below and above the threshold — must carry a unique exchange-provided identifier so the whole chain is auditable: client to Algo-ID to static IP to API key. If your automation is placing orders that are not tagged, raise it with your broker immediately, because untagged automated flow is exactly what the framework is designed to stop. 8. Know the kill switch and audit-trail obligations Brokers must provide a “kill switch” — an emergency stop that can disable a malfunctioning algo instantly — and must retain detailed API and order logs (commonly cited as at least five years) for audit. As a retail trader, know how to trigger the kill switch on your platform and keep your own copy of your strategy logic and order logs so you can reconcile if anything goes wrong. RequirementBelow OPS thresholdAt or above OPS threshold Algo registration with exchangeNot required for personal useRequired, via your broker Broker-approved API (OAuth + 2FA + static IP)RequiredRequired Order tagging (Algo-ID)RequiredRequired Permitted order typesLIMIT / DAY only (no MARKET or IOC)LIMIT / DAY only (no MARKET or IOC) Re-approval on logic changeNot applicableRequired Who can run itSelf or immediate-family accountsRegistered, monitored algo Not sure whether your TradingView-to-broker setup is on the right side of these rules? I audit and rebuild automation bridges for compliance regularly — message me on WhatsApp at +91 77352 68199 and I will tell you where you stand. Key dates on the glide path SEBI let ready brokers go live from 1 October 2025 and set milestones for the rest: submitting registration applications for retail algo products and at least one strategy by 31 October 2025, completing registration by 30 November 2025, and joining a mock session with the new functionality in early January 2026. Brokers that missed these milestones could be barred from onboarding new retail API-algo clients from 5 January 2026, and the framework became fully mandatory on 1 April 2026. If your broker was slow to comply, that is worth asking about directly. How this changed my client automation builds The biggest practical shift I saw was around IP addresses and tagging. Several bridges I had built ran on cloud servers with rotating IPs — cheap and convenient, but exactly what the framework disallows. I moved those clients onto fixed static IPs and reworked the order layer so each request authenticated through the broker's OAuth flow and carried the broker's algo tag rather than a generic order type. The other recurring fix was frequency and order type. A few clients were firing rapid modify-and-cancel orders that flirted with the OPS threshold without realising it, and others were still sending market orders. We throttled the logic to stay comfortably under the limit (or planned exchange registration where the strategy genuinely needed the speed) and converted market orders to limit orders. If you want that groundwork done properly, my Pine Script development and MT4/MT5 automation services build compliance in from the start. For broker-specific wiring, my guides on Zerodha Kite Connect API pricing and rate limits and Fyers webhook setup cover the API side, and if you write your own code, read my developer's guide to building SEBI-compliant algos for Zerodha and Fyers. Frequently asked questions Is algo trading legal for retail traders in India in 2026? Yes. As of July 2026, retail algo trading through broker-approved APIs is explicitly permitted under SEBI's 2025 framework, provided you follow the API-security, tagging and (where applicable) registration rules. It is regulated, not banned. Do I need to register my algo with SEBI or the exchange? Only if your algo places orders above the order-per-second threshold (currently 10 OPS per exchange). Below that, a personal strategy in your own or immediate-family accounts generally does not need registration — but it still must run through a compliant, tagged API. Registration, when required, is done through your broker with the exchange, not directly with SEBI. What is the Algo-ID and do below-threshold algos need it? The Algo-ID is a unique identifier the exchange assigns so every automated order can be traced. Under the framework, all algo orders — below and above the threshold — are tagged, so yes, even a low-frequency personal algo's orders should carry a tag from 1 April 2026. Can I still use TradingView webhooks with an Indian broker? You can, as long as the orders route through your broker's approved API with OAuth and 2FA, a static IP, permitted order types and proper tagging. The webhook itself is only the trigger; compliance lives in how the order reaches the exchange. Confirm your specific setup with your broker. What happens if I ignore these rules? Non-compliant access can be blocked by your broker, and unregistered above-threshold algos can be disallowed. Because responsibility sits with brokers, they are motivated to shut down setups that do not fit the framework. Always confirm the current requirements before going live rather than after an order is rejected. If you would rather not decode circulars yourself, I will review your strategy, broker and API setup against the current rules and rebuild anything that does not fit. Message me on WhatsApp at +91 77352 68199 to get started. This article is general information current as of July 2026 and is not legal, financial or investment advice. SEBI and exchange rules on algorithmic trading can change, and operational details differ by broker — always verify the current requirements directly with SEBI, NSE/BSE and your broker before automating. Algorithmic and automated trading carries real financial risk, including rapid losses from software errors or connectivity failures; no strategy or automation guarantees profits. Trade only with capital you can afford to lose.

algo trading compliance 2026

SEBI Algo Trading Rules 2026: Retail Compliance Checklist