As per SEBI regulations on retail algorithmic trading, order placement is allowed only when specific compliance requirements are met. If you're facing order placement restrictions or seeing related error messages, check the scenarios below to identify and resolve the issue.
Common error messages
- Order placement restricted. Algo orders are not allowed from this app.
- Request rejected. Orders are only allowed from whitelisted IP addresses. This request was received from IP: XXXXXXXX
Troubleshooting scenarios
Scenario 1: Static IP not whitelisted or new App not activated
What’s happening:
Your request is being rejected because the static IP is not registered or the new App is not activated.
What to do:
- Go to the API Dashboard.
- Update and whitelist your static IP address
- Ensure you are using the newly created App
For complete steps, refer to this article.
Scenario 2: Incorrect App credentials are used
What’s happening:
Orders are failing because old App credentials are being used instead of the new App credentials.
What to do:
- Use the new credentials from the API dashboard
- Replace existing App ID and Secret in your setup
- Ensure the correct App ID is used
- Ensure App type = 200 is passed
Scenario 3: Request is sent from a non-whitelisted IP
What’s happening:
The request is being sent from an IP address that is different from the whitelisted static IP.
What to do:
- Verify the outgoing IP address of your server
- Ensure it matches the whitelisted static IP
- Check for:
- Proxy or VPN interference
- Load balancer or cloud setup using a different IP
For details on validating your IP address, refer to this guide.
Before placing orders, ensure
- Static IP is correctly whitelisted
- New App is activated
- Correct App credentials are used
- App type = 200 is included in requests
- Orders are sent only from the whitelisted IP
Important: Order placement will fail if the App configuration or static IP does not match the required setup.
Tip: Most issues occur due to mismatch between App credentials and static IP. Verify both together.
Still facing issues?
If the issue persists, contact our support team and share:
- App ID (new)
- IP address used for the request
This will help us assist you faster.
Last updated: 02 Apr 2026
Related Articles
What are the new SEBI rules for retail algo trading from April 01, 2026?
SEBI has introduced a new regulatory framework for retail algo trading, effective April 01, 2026. These changes apply to users running automated trading strategies using the FYERS API or third-party platforms. What changes from April 01, 2026? Static ...
What is Algo Trading?
Algo trading is a system of trading wherein simple or complex trading strategies are defined into algorithms which can then execute trades on the basis of the predefined parameters. It executes orders using automated or semi-automated pre-programmed ...
How do I activate the new App for API trading after April 1, 2026?
As per retail algo trading regulations, API trading must be migrated to a compliant setup before April 1, 2026. Existing API apps created under the previous setup will not be allowed to place orders. To continue API trading without disruption, ...
What functionalities does the order websocket in API v3 offer?
The order websocket in API v3 is an advanced feature that provides access to a richer set of information related to trading. It includes updates on orders, trades, and positions, as well as alerts and EDIS (Exchange Data Interface System) details. ...
What is a Multi-Leg Order and how is it different from the Multi Order API (Bracket Order)?
A Multi-Leg Order is a feature that allows users to execute multiple legs simultaneously, providing hedging benefits and ensuring that all legs of the order are executed together. This differs from the Multi Order API, where each leg is sent to the ...