If you use the FYERS API to run algo strategies using your own trading setup or third-party platforms, this matters.
SEBI has introduced a new framework for retail algo trading. It comes into effect on April 1, 2026. These changes are mandatory, and if you are not prepared before the deadline, your automated strategies will stop working.
Here’s what changes from April 1:
1. Static IP address
The API will only accept orders from a registered App ID tied to a whitelisted static IP. One app, one IP. Orders from any other source are automatically rejected.
2. 2FA authentication
You will need to complete 2FA once every day. The refresh-token flow that kept systems running continuously is being discontinued.
3. 10 orders per second is the limit
Anything above that gets rejected. This includes order placement, stop loss, targets, and order modifications.
4. Market orders are not allowed
They will be automatically converted to MPP (Market Price Protection) orders, which add a price protection band around execution. The behaviour is similar, but if your strategy depends on true market order fills, account for this.
AMO orders are not permitted in algo trading. Therefore, ensure that the “offlineOrder” parameter is always set to false when placing orders through the API.
5. Third-party platforms must be empanelled and hosted inside the broker’s infrastructure.
A lot of traders run algo strategies through external platforms that connect to the FYERS API. These platforms sit outside FYERS, on external servers. Under the new rules, such platforms can only place orders if they are empanelled and hosted within the broker’s own systems. Most external platforms do not meet this bar. If yours does not, your orders will not go through starting from 1st April.
Orders originating from InstaOptions or any API bridge will not be allowed.
What should you do?
If you want to continue using your existing setup, here is what needs to be in place before April 1.
- Get in touch with your internet service provider or cloud service provider to get a static IP
- Update the static IP in the FYERS API Dashboard
- Activate the trading app, click here for details
- Get new app credentials
- Use the new app credentials in your trading setup
For a full breakdown of all the regulatory changes and what they mean, read this.
A simple alternative: FYERS Automate
If you do not want to deal with static IPs, registering a new App ID, or waiting to see whether your third-party platform gets empanelled in time, there is a simpler option.
Automate lets you run your strategies directly inside the FYERS platform. Because it runs within FYERS infrastructure, it already meets the requirements of the new framework. You do not need to worry about static IP whitelisting, external servers, or platform empanelment.
What you focus on is the strategy. Automate handles the execution.
Automate is a no-code visual strategy builder where you create workflows using the same logical structure traders already follow: triggers, conditions, and actions. The logic remains fully flexible.
If your signals already come from somewhere else, like TradingView alerts or your own scripts, they can be connected to Automate using webhooks. Your signal generation stays exactly the same while execution moves inside FYERS.
You can also manage the entire lifecycle of a trade on the same workflow: entries, exits, multi-leg orders, and portfolio-level risk checks.
Do this before March 31
The current framework and the new one run in parallel until March 31. That is your window to move over without any disruption.
To understand Automate in depth before you build, start with this blog and
https://www.youtube.com/watch?v=3ZB37Ofor34
. Every block of triggers, conditions, and actions is covered.
Or go directly to Automate on FYERS Web and start building. Pick one strategy you are already running and set it up. You will have it live in under fifteen minutes.
For additional assistance or help, you can fill this form.
