I am developing a self-built Kite Connect system for my own Zerodha account, covering Indian NSE/BSE futures and options. It would generate signals, apply account-wide risk checks, and, only after testing and my approval, potentially place, modify, cancel, and exit orders automatically. I am not offering it to other investors.
Please route this request to the team responsible for the permitted API trading route and confirm in writing:
1. Is unattended, rule-based order submission permitted for my own retail account through Kite Connect? If so, what exchange registration, algo identification, order-rate limits, approval, or other conditions apply? If not, what level of manual confirmation is required? 2. What are the current static-IP and authentication requirements for placing, modifying, and cancelling orders, including a backup egress IP? 3. Which current order types and exit methods are permitted for NSE/BSE F&O through the API, including market protection, IOC, stop orders, and multi-leg workflows? 4. Your public API documentation describes a Kite sandbox, while a support article says no sandbox is offered. Is it presently available to my developer account, and which order-lifecycle functions can it test? 5. May I privately retain Kite market quotes, instrument masters, and historical candles for my own historical replay, backtesting, paper trading, and private dashboard? Please specify retention limits, restrictions on using another broker's data alongside Kite data, and any additional permissions needed. I will not redistribute the data. 6. Which Console reports or API endpoints should I use for an authoritative opening cash/position baseline, historical orders and trades, final charges, and settlement reconciliation?
Please provide links to current applicable terms and the process for any required approval. My system will remain disabled for live order writes while I resolve these questions.
1. Automated order placement and exchange requirements For retail algo trading, the threshold is 10 orders per second (OPS) per client ID. If your order rate exceeds this threshold, exchange registration and an algo ID may be required. Strategies placing up to 10 orders per second (OPS) do not require exchange registration or an algo ID.
2. Static IP and authentication A registered public static IP is required for API order placement. You can configure primary and secondary IPs through the Developer Console. IP updates are limited to once per calendar week. Ensure that you follow the documented login flow and use a valid access token.
3. Supported order types The API supports MARKET (with market protection), LIMIT, SL and SL-M (with market protection), subject to exchange and instrument restrictions. DAY and IOC validity are supported, with TTL available where applicable. Certain order types, including SL-M for index options, may be restricted.
4. Sandbox availability The sandbox is currently unavailable to API users. We will provide an update if it becomes available.
5. Market-data usage Kite Connect data may be used for personal analysis. Permanent data storage and paper trading using live market data are restricted. You may use data from other providers alongside Kite data.
6. Account records and reconciliation: For information on funds, margins, holdings, positions, daily orders and trades, please refer to the relevant sections of the Kite Connect API documentation.
Final charges and historical reconciliation: Refer to Console reports, including contract notes, tradebook, ledger and P&L reports, as applicable.
For retail algo trading, the threshold is 10 orders per second (OPS) per client ID. If your order rate exceeds this threshold, exchange registration and an algo ID may be required. Strategies placing up to 10 orders per second (OPS) do not require exchange registration or an algo ID.
2. Static IP and authentication
A registered public static IP is required for API order placement. You can configure primary and secondary IPs through the Developer Console. IP updates are limited to once per calendar week. Ensure that you follow the documented login flow and use a valid access token.
3. Supported order types
The API supports MARKET (with market protection), LIMIT, SL and SL-M (with market protection), subject to exchange and instrument restrictions. DAY and IOC validity are supported, with TTL available where applicable. Certain order types, including SL-M for index options, may be restricted.
Refer to the Orders API .
4. Sandbox availability
The sandbox is currently unavailable to API users. We will provide an update if it becomes available.
5. Market-data usage
Kite Connect data may be used for personal analysis. Permanent data storage and paper trading using live market data are restricted. You may use data from other providers alongside Kite data.
6. Account records and reconciliation: For information on funds, margins, holdings, positions, daily orders and trades, please refer to the relevant sections of the Kite Connect API documentation.
Final charges and historical reconciliation: Refer to Console reports, including contract notes, tradebook, ledger and P&L reports, as applicable.
The back-office APIs are currently unavailable.