India broker clamps APIs
Indian broker FYERS is disabling API order placement for third‑party platforms ahead of SEBI algo‑trading rules taking effect April 1 — traders will need alternate execution routes or self‑built systems. The move highlights immediate compliance friction for retail and quant traders in India and could shift orderflow to native or in‑house algos (x.com).
FYERS says it has discontinued new API Bridge subscriptions and renewals effective March 5, 2026. (fyers.in) The broker’s community post clarifies third‑party platforms that sit outside FYERS’ infrastructure will face order‑placement changes under the new retail‑algo framework. (fyers.in) SEBI’s retail algo framework becomes fully mandatory on April 1, 2026 and requires empanelment, broker oversight, and traceability for every algorithm deployed to execute trades. (sahi.com) The Feb. 4, 2025 SEBI circular that underpins the regime sets broker responsibilities for API security, unique strategy identifiers, and exchange‑level surveillance requirements that vendors and brokers must follow. (taxguru.in) Common third‑party front‑ends named in FYERS’ integration materials—TradingView, Amibroker, MT4/MT5, NinjaTrader and Excel VBA—are the exact platforms likely affected by API Bridge subscription changes. (fyers.in) FYERS’ product page advertises order placement latency under 75ms and capacity up to 100,000 API requests per day, metrics that traders will weigh when choosing between broker‑hosted execution and native/in‑house algo options. (fyers.in) The timeline compresses toward April 1: FYERS’ March 5 change removes a subscription path weeks before SEBI’s April 1 compliance deadline, forcing third‑party vendors and retail users to complete empanelment or migrate execution ahead of that date. (fyers.in)
