NSE Algo Trading: What the Exchange Asks of Retail Traders
NSE algo trading for retail investors means using automated rules to send orders through your broker's API, under implementation standards that the National Stock Exchange (NSE) published on 5 May 2025 in circular NSE/INVG/67858. In short: you need a static IP address registered with your broker, every algo order carries an exchange-issued ID, algo providers must be empanelled with the exchange, and above 10 orders per second an algo must be registered. Your broker, not you, applies most of these controls.
Risk note, up front: trading carries risk, and automation does not reduce it. A flawed rule loses money faster when software runs it. This article explains an exchange's rules. It is education, not investment advice, and it names no strategy, signal or expected return.
What is the NSE circular about?
The circular, titled "Safer participation of retail investors in Algorithmic trading", sets out the exchange's implementation standards under SEBI's circular dated 4 February 2025. SEBI (the Securities and Exchange Board of India) is the market regulator, and the exchange turns its framework into operating standards that brokers must follow. You can read the original on NSE's site: NSE/INVG/67858. For the bigger picture of who does what, see algorithmic trading in India: who sets the rules.
What does a retail trader need to use an API on NSE?
According to section A of the circular:
- A static IP address. A static IP is an internet address that does not change. Clients must give the broker one or more static IPs to get API access. A client may give a primary and a secondary one for backup.
- One or more API keys. A client can have several keys, for example for different segments or different algos. The broker makes sure unregistered algos run only through one predefined key.
- Limited changes. You can update your mapped static IP no more than once a calendar week, with room to ask the broker in extraordinary cases.
- One client per IP. A static IP can be mapped to only one client at a time, unless the clients belong to the same family as SEBI defines it.
- Daily logout. All API sessions must be logged out every day before the next trading day starts, so a program has to log in again and restart cleanly.
What is the 10 orders-per-second threshold?
The Threshold Orders Per Second (TOPS) is a speed limit that decides whether an algo has to be registered. The circular sets it initially at not more than 10 orders per second per exchange and segment, and the exchanges can change it after notice to the market (section B point 2 and section F).
| Your order speed through the API | What the circular says |
|---|---|
| Within the threshold (up to 10 orders per second) | Section B point 2 says you need not register the algo from the broker's system, but section B point 3 says exchange registration and a generic algo ID apply. The broker must still apply risk checks and can set its own, lower limit for you. |
| Above the threshold | You must register the algorithm with each exchange where you plan to use it. The broker passes your details to the exchange, which issues a registration ID (section C). |
| Orders sent above the broker's limit | The broker can reject or not process them. |
A caution: the published text is inconsistent for orders below the threshold. Section B point 3 says they require exchange registration and a generic algo ID, while section B point 2 and section G describe them as registration-free. Section C point 1 is clear that registration applies when you go above the threshold. Ask your broker in writing how your setup is classified, and check the current NSE text.
Also note that every algo order, registered or not, is tagged with a unique identifier from the exchange to create an audit trail (section G).
What happens if I use a third-party algo provider?
Section E says algo providers must be empanelled with the exchanges, must register each of their algos, and the exchange assigns a unique algo ID to each. A broker that works with an empanelled provider must tell the exchanges. The broker must also do due diligence on the provider and report misconduct.
This matters when you read a vendor's pitch. A provider that cannot tell you which exchange it is empanelled with, or which broker carries its orders, has not answered the first question that the circular asks of it.
What does the broker have to do?
The circular puts a lot on the broker (sections H and I):
- keep an audit trail of API orders and trades, available for at least 5 years;
- use OAuth-based authentication and two-factor authentication for client access;
- make sure open APIs are not allowed, with access only through a client-specific API key and a static IP the broker has whitelisted;
- be "fully responsible and liable" for all orders that come through its API systems.
The circular also says the exchanges have the authority to kill any rogue algo that is affecting the market (section J).
A worked example: checking your setup
Here is a checklist you can run with your broker. The numbers are the circular's own, nothing else is assumed.
- Ask if the broker offers API access to retail clients, and what it needs from you (static IP, which API key for which algo).
- Estimate your peak order rate. If your program sends a handful of orders a day, it is far below 10 per second. If it sends bursts, count them per second, per exchange.
- Ask how the broker classifies your setup and what you must register, if anything.
- Check the provider, if you are using one: which exchange empanelled it, and what algo ID applies.
- Plan for the daily logout. Make sure your program can log in again each morning and does not retry orders in a loop after a disconnect.
What can go wrong?
- Rule risk: the logic is flawed or only fit past data. See how to backtest a trading algorithm and paper trading vs live trading.
- Technical risk: a changed IP, an expired login or a dropped feed can stop or distort your orders.
- Vendor risk: a seller who promises returns. Treat any promised return as a warning sign.
- Credential risk: anyone with your API key can place orders in your account. Never share it.
Frequently asked questions
Is algo trading allowed on NSE for retail investors?
Retail investors can use algos through a broker that provides API access under the standards above. For the legal position and dates, read is algo trading legal in India.
Do I need to register my own algo with NSE?
According to the circular, registration applies when you place orders faster than the threshold (initially 10 per second per exchange). Below it, the text is inconsistent (see the caution above), but your broker still applies risk checks and your orders are tagged. Confirm your case with your broker.
Do I need a static IP?
Yes, for API access to place orders the broker requires a static IP from the client, or the vendor's or broker's static IP in the cases the circular lists.
Who is responsible if an algo order goes wrong?
The circular says the broker is fully responsible and liable for orders from its API systems, but that does not remove your own risk of loss. Set order size and loss limits yourself.
What this article does not cover
It does not cover other exchanges, specific brokers' processes, tax, or any strategy. It is not legal or investment advice. Exchange and SEBI circulars can be amended, so confirm the current text on NSE's website and with your broker before you act. Trading carries risk, and you can lose money.