Since the February 2025 circular on safer participation of retail investors in algorithmic trading, every conversation about automation in India starts with the same question: am I still allowed to run my own code? The short answer is yes, within a framework. Here is the shape of it, stripped of circular-speak. None of this is legal advice; confirm specifics with your broker and the current exchange circulars, because the implementation timeline has already moved more than once and ran in phases towards April 2026.

Why it exists

Retail participation in derivatives grew faster than the guardrails around automated access to it. Unregulated vendors were selling opaque strategies with impressive claims and no accountability, running on client accounts through broker APIs that nobody was tracking. When those strategies failed, there was no audit trail and nowhere to complain. The framework's core idea is simple: if an order is generated by a machine, somebody identifiable is responsible for that machine.

The three roles

  • The broker is accountable for API access, for registering algos with the exchange, and for tagging orders with a unique algo identifier.
  • The algo provider or vendor must be empanelled through brokers with the exchanges, and faces heavier requirements when the strategy logic is undisclosed.
  • The client — you — is responsible for using registered algos through your registered access, within the limits your broker sets.

White box, black box

A white-box algo is one whose logic is disclosed to the user: you can see the rules and reproduce the decisions. A black-box algo hides the logic. The framework treats the second category more strictly, because a user cannot evaluate what they cannot see. If you write your own strategy, you are by definition in white-box territory with respect to yourself.

The orders-per-second threshold

API usage below a prescribed order rate — set at the level of a few orders per second per exchange — is not treated as algorithmic trading requiring registration. Above it, registration through your broker applies. Practically, a swing or positional system firing a handful of orders a day sits comfortably below the line; an execution algorithm slicing a large order does not.

What actually changes for a self-coded trader

  1. Your API access will be tied to registered static IPs and to a specific approved usage pattern. Expect your broker to ask for this.
  2. If your system places orders above the threshold, expect registration and a unique algo ID attached to your orders.
  3. Expect your broker to ask for a description of what the algorithm does — which is a good reason to have written that specification anyway.
  4. Sharing your algorithm with others, or selling it, moves you towards the provider category, with the obligations that follow.

The honest upside

The paperwork is real, and for a single trader running one strategy it is mostly a one-time cost. What it buys is a market with fewer operators promising forty percent a month from a black box that nobody can inspect. If you have ever had to explain to a family member why the "guaranteed" algo they subscribed to has stopped responding, you will take that trade.

This note is engineering and compliance commentary, not legal or investment advice. Read the circulars, and ask your broker.