As regulatory standards around retail algorithmic trading and API -based trading continue to evolve, ensuring compliance without compromising ease of use has become critical for traders. In line with SEBI and exchange-led initiatives to strengthen market safety and transparency, we are now going live with the adaptation of the SEBI circular no. SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2025/0000013.
At Flattrade, we view regulatory change as an opportunity to simplify and enhance the client experience. To support our clients through this transition, we are introducing controlled API key management and launching Flattrade API Version 2, designed to fully adapt SEBI guidelines.
What We Are Launching
Introduction of Flattrade API Version 2 (From 12 January 2026)
To further align with SEBI and exchange guidelines, Flattrade is launching API Version 2.
API Version 2 introduces the following additional restrictions/controls:
- API keys can be generated only by providing a Redirect URL and a Static IP
- Orders can be placed/modified/canceled only from the Static IP
- You can generate only one API key for non-registered algos to generate fewer than 10 orders per second
- You can generate a separate API key registered alogs to generate more than 10 orders per second
- Only limit or SL-Limit orders are allowed
- Cover Orders and Bracket orders are not allowed
- IOC orders are not allowed for the commodity segment
Static IP
While it is mandatory to provide a primary static IP, a secondary static IP is optional. You are allowed to modify the primary or secondary static IP once in a calendar week. These static IPs should be unique across our clients. With respect to sharing the static IP for our clients who belong to one family, this is not enabled in our system yet. But you can be assured that we are working on this.
Version 2 Adoption
To make our clients (who are already using our Flattrade API version 1) transition to our new Flattrade API version 2, we kept things simple.
- No change in our existing OAuth flow to generate a token every day
- All our API’s still follow the same signature
- Process to generate a new API key remains the same
- The only change is in the subscription process to our web socket. Please refer to our Pi documentation for the same.
Documentation of Flattrade API Version 2:
Our existing API documentation portal pi.flattrade.in is now updated with the version 2 changes. You can refer to the new URL for the API and web-socket on this portal.
These changes are aimed at improving control, security, and alignment with Static IP-based authentication, while ensuring uninterrupted access for compliant API users.
Discontinue / Sunset of Flattrade API version 1
We understand you need time to adapt to our Flattrade API version 2. So we will continue to have our Flattrade version 1 in LIVE for the next few weeks. But changes below will be effective from 12 January 2026.
- You cannot have more than one API key
- In case you already have more than one API key, starting from 12 January 2026, you will only be able to use the last-used API Key. All other API keys will be deleted
- You will be allowed only to modify the API secret, redirect URL, and postback URL of the API key
- In case you have taken a session token with Version 2, then any session token with Version 1 will be automatically disconnected. Similarly, if you have taken a token with Version 1, then any session token with Version 2 will be automatically disconnected.
- In case if you have not taken an API key before, you are still allowed to take one API key under Version 1. But we recommend that you adopt Version 2 directly.
Why Flattrade Is Introducing These Changes
These enhancements are being introduced to:
- Ensure full compliance with SEBI and exchange regulations on API and retail algorithmic trading
- Enable smooth adoption of the mandatory regulations
- Strengthen platform security, traceability, and operational stability
- Reduce complexity for clients during regulatory transition
- Offer a future-ready API ecosystem that supports both retail and advanced algorithmic strategies
Our objective is clear: help clients stay compliant without adding unnecessary friction to their trading workflows.
Regulatory Context: SEBI & Exchange Guidelines
SEBI, along with the exchanges, has issued circulars focused on safer participation in algorithmic and API-based trading. These guidelines introduce:
- Mandatory Static IP mapping for API orders
- Exchange approval for high-frequency and advanced strategies
- Strategy-level disclosures and documentation
- Defined governance for API vendors and users
These measures are intended to enhance market integrity, improve accountability, and protect investors. Flattrade’s API enhancements are fully aligned with these regulatory requirements and designed to operationalise them in a client-friendly manner.
How This Helps Clients Transition Smoothly
We recognize that these compliance can be operationally demanding, particularly for clients running automated systems. Flattrade’s approach simplifies this transition by:
- Clearly categorizingclients based on order frequency
- Enforcing Static IP requirements at the API level with predictable update limits
- Minimizingapproval and documentation requirements for low-frequency users
- Providing a structured approval workflow for high-frequency and advanced strategies
- Allowing parallel usage of API Version 1 and Version 2 during the transition period
This phased roll-out ensures clients have sufficient time to adapt their systems while continuing to trade without disruption.
Clients are encouraged to begin migration to API Version 2 well in advance to ensure uninterrupted trading operations.
Flattrade’s new API framework reflects our commitment to combining regulatory compliance with client-centric design. By introducing API Version 2, we are enabling our clients to continue trading confidently in a secure, transparent, and regulation-aligned environment.
Our API and support teams will continue to assist clients throughout this transition with documentation, onboarding guidance, and dedicated technical support.




