NSE API Algo Reclassification: What It Means for Order Flow

From April 1, 2026, NSE's NNF (Now or Never Fill) classification framework reclassified API-routed orders as algorithmic orders. The 13th digit of the NNF field now carries that distinction for the exchange.

The market gets a cleaner regulatory label. The trader still faces the same practical problem: how do we read what the order did once it reached the exchange?

Terms used in this note: COT, Initiative Buying / Selling (IB/IS), Absorption, Auction, IB30/IS30.

The routing label matters for compliance, reporting, and market structure documentation. It tells us something about how an order entered the system. It does not tell us whether the order created initiative buying, initiative selling, absorption, exhaustion, or continuation.

That part still has to be read from the tape.

Order Flow reads the transaction, not the route.

Order Flow works at the price level. It asks whether bids were hit, offers were lifted, and whether that activity changed the auction. The 13th digit of the NNF field tells the exchange how the order was routed. The chart tells the trader whether the order mattered.

This has not changed with the April 2026 reclassification. The footprint on a Nifty or BankNifty Order Flow chart is the transaction record — not the routing record. An API order that gets absorbed at a prior-day POC reads the same as any other order that gets absorbed at that level. COT turning at the same price on repeated tests is the read that matters, not the origination channel.

The market-order restriction, exact wording

From NSE's retail algo FAQ:

• Point 8.1.1.12 of NSE circular NSE/MSD/67753 dated April 29, 2025: "Algo orders with order type as Market Order are not permitted."

• Point 8.1.2.1 of the same circular, for commodities: "Immediate Or Cancel (IOC) and Market orders shall not be allowed to be placed using algorithmic trading."

The restriction is enforced at two layers. The broker is expected to block it at the front end. If it gets past the broker, the exchange has a pre-emptive rejection mechanism that filters algo-tagged market orders at the gateway. That mechanism was first deployed in Currency Derivatives via NSE/CD/67733 dated April 28, 2025, extended to Commodities (NSE/COM/68215, May 28, 2025), then Cash (NSE/CMTR/68802, June 30, 2025), then F&O (NSE/FAOP/69296).

So in the F&O segment — where most derivatives flow sits — algo-tagged market orders are rejected by the exchange before they can hit the book.

NNF, NEAT, and what the 13th digit does

NNF stands for Non-NEAT Front End. NEAT is the exchange's own native terminal. NNF is the standardised wrapper for everything else: broker terminals, OMS systems, internet trading, dealer platforms, client APIs, vendor APIs. Almost all retail-facing order flow on NSE rides on NNF.

Every order that leaves an NNF terminal carries a 15-digit NNF identifier. The 13th digit is the classification switch. As laid out in NSE/INVG/69255 dated July 22, 2025 (Detailed Operational Modalities — Retail Algo):

The first 12 digits identify the origin. The 13th digit identifies the nature.

For Client Direct API, the first 12 digits are fixed at 444444444444, and the 13th digit must be 0, 2, or 4 — all algorithmic. There is no path for an API order to be tagged as non-algo at the exchange level.

That is the structural change. The exchange is no longer classifying orders by who sent them. It is classifying them by how they arrived.

What the order classifier sees vs. what the trader sees

A manual click on a broker app sends a non-algo order. 13th digit = 1.

The same trader, running the same logic, sending the same order through the broker's API, sends an algo order. 13th digit = 0.

Same person. Same intent. Different classification.

This matters because the algo classification carries downstream restrictions:

• Market orders are blocked at the gateway.

• IOC orders are blocked in commodities.

• An Algo ID is required if order rate exceeds 10 orders per second (OPS).

• Static IP whitelisting is mandatory.

• The broker must maintain a 5-year audit trail of every API order.

For sub-10-OPS retail flow, registration of the strategy is not required, but the order still travels through the algo pipe and is tagged accordingly.

Smart Candlesticks place the activity inside bar structure.

Smart Candlesticks connect order activity back to the candle. A candle that closes strong but contains poor internal acceptance should not be treated as clean strength. A candle that looks ordinary but carries IB30 or IS30 activity at a structural level deserves attention — regardless of how those orders were routed to the exchange.

The reclassification affects what brokers must report and how members register with NSE. It does not affect how acceptance and rejection appear on the Smart Candlestick chart.

MFLOW separates fresh participation from defensive activity.

MFLOW asks whether a move is new business or old business. This matters because a routing change may alter the visible composition of orders on an exchange report without changing the underlying participation quality. Fresh institutional entry reads differently from short covering or long liquidation — and that distinction is available in MFLOW independent of how NSE classifies the originating order.

The practical workflow after the reclassification:

1. Treat the NSE NNF classification as a routing and compliance fact.

2. Treat the traded activity as auction evidence — separate question.

3. Use Order Flow to read aggression at the price level.

4. Use Smart Candlesticks to place that aggression inside bar structure.

5. Use MFLOW to judge whether participation is new or defensive.

The wrapper changed. The auction still has to be read.

What this changes on the Orderflow tape

The change at the infrastructure layer maps to a change in how aggressive participation reads on a Orderflow chart.

Aggressive participation on Orderflow shows up as trades hitting the bid or lifting the offer at market. That used to come from two distinct populations: discretionary retail clicking market buy or sell, and algorithmic flow sweeping liquidity. After the framework took effect, the discretionary-via-API portion of that aggressive flow can no longer enter as a market order. It now enters as a limit at touch or as a limit-with-protection. The exchange still records the cross when it executes, but the order type has shifted.

That has a subtle effect on the read:

• Initiative activity (the IB/ IS signal — Initiating Sell / Initiating Buy on the desk's framework) still appears clearly when participants take the offer or hit the bid with size. The execution prints the same way on the tape. What thins out is the noisy retail market-order layer that used to sit underneath it. The signal-to-noise on initiating prints improves.

• Responsive activity (the RB signal — Responsive Buy in the desk's reading of inventory-driven response) is unchanged in structure, because responsive participants were already working limits at value extremes. They were never the population sending blind market orders.

• Intent at extension is now easier to separate. When the tape shows aggressive lifts at the top of a range under the new regime, fewer of those lifts are retail panic clicks routed through an API. More of them are deliberate.

The framework does not change Orderflow. It changes the composition of what generates Orderflow. The cleaner the input, the cleaner the read.

Why this is happening at all

The framework's policy goal, as stated in the SEBI circular, is "safer participation of retail investors in Algorithmic trading." The structural goal is auditability.

Before April 2026, an API order and a manual order from the same client were indistinguishable at the exchange layer. The exchange could see the broker, the segment, and the instrument, but not whether the order was generated by a human click or by a script. Algorithmic flow was supposed to be tagged, but tagging was uneven and largely self-reported.

The 13th-digit rule and the fixed 444444444444 for Client Direct API close that gap. Every order now carries its origin in its identifier. Every API order is, by definition, algo. The exchange can audit the full population of algorithmic orders by reading the 13th digit alone.

That is the structural change. The market-order ban is a downstream consequence of it.

What the desk watches now

Three things are observable on the tape since April 1:

1. The composition of aggressive prints in active F&O contracts. Market-order rejections at the gateway thin out a class of order that used to generate prints at extreme prices in fast markets.This is actaully positive in the Options market where the siganlling has been cleaner.

2. The shape of bid/offer cancellations around news prints. Algo activity is now more clearly tagged, and the pattern of withdrawal at velocity is easier to distinguish from manual hesitation.This has made news based OF reading easier for most of us. When they come, we just know.

3. The Orderflow at session opens and at IB completion. With market orders from APIs gone, opening drives that hold their levels look different from opening drives that don't — the noise component is lower. The past few weeks of Opening moves have had high signal intent and been clean.

None of this is theory. It reads off the tape if the chart is set up to show it.

Related reading: From Tape Reading to Algorithms — how execution intelligence has evolved across NSE's history and why the read-the-tape approach has survived each transition. When the Wrapper Changes But the Intent Doesn't — the same argument applied to order routing labels more broadly. The Progressive Guide to Order Flow Analysis — a structured sequence from aggression reading to full auction context.

For the complete tool sequence, start with the Vtrender Learning Pathway. To practice on live Nifty, BankNifty, Sensex, and Bankex data, open Vtrender Charts.