kite connect rate limits

As of July 2026, the Zerodha Kite Connect API costs ₹500/month per API key for the paid "Connect" plan, which now includes live WebSocket market data and historical candle data at no extra charge. A free "Personal" tier covers order, GTT and alerts management but streams no market data. The core rate limits are 10 orders/second, 400 orders/minute and 5,000 orders/day, with quote requests capped at 1/second and historical candles at 3/second. Automated trading is allowed under SEBI's retail algo framework (fully mandatory from 1 April 2026), but you must whitelist a static IP before you can place a single order through the API. In my 8 years building Pine Script strategies and Kite Connect bots for clients across 14+ countries, the biggest billing surprise I still un-teach is the old "₹2,000 for Connect plus ₹2,000 for historical data" pricing that people quote from stale 2019-era blogs. Zerodha retired that model. The number you actually pay in 2026 is much smaller, and the real cost of running an algo has shifted from the API fee to compliance plumbing. Here is exactly what you pay, what you are limited to, and what the law now requires. Kite Connect API pricing in 2026 Kite Connect has two tiers. You sign up at developers.kite.trade, create an app, and either stay on the free Personal plan or subscribe to Connect for ₹500/month per API key. PlanPrice (2026)What's included PersonalFreeFull order, GTT (Good Till Triggered) and alerts management; margin computation; portfolio management. No live or historical market data. Connect₹500 / month per API keyEverything in Personal, plus live market data over WebSockets and historical candle data. Startups (mass retail apps)Free (on approval)Kite Connect APIs offered free of charge for platforms serving retail users at scale; you email the Kite Connect team. Two points that trip people up: There is no separate historical-data add-on any more. Both live and historical data are bundled into the single ₹500/month fee. You cannot, however, buy historical data on its own — you must hold an active Connect subscription first. The fee is per API key, not per Zerodha account. If you run three separate apps under one developer account, you pay for each subscribed key. Charges are collected either via Razorpay or debited from your Zerodha trading account, and invoices are downloadable from your developer billing page or Console. If you are still weighing whether to code against the API yourself or start with a no-code webhook bridge, my walkthrough on the easiest way to connect TradingView alerts to Zerodha is the cheaper first step for many retail traders. Kite Connect API rate limits (2026) Rate limits are enforced per API key, and breaching them returns an HTTP 429 Too many requests. These are the official published limits: EndpointRate limit Quote (market quotes)1 request / second Historical candle data3 requests / second Order placement10 requests / second All other endpoints10 requests / second On top of the per-second caps, Zerodha applies hard risk-management ceilings: 10 orders per second and 400 orders per minute per client account. 5,000 orders per day per user/API key, across all segments and varieties. Critically, this counts both successful and rejected orders — a buggy loop firing invalid parameters will burn through your daily quota even though nothing shows in your order book. 25 modifications per order maximum; after that you must cancel and re-place. The 1 request/second quote limit is the one that catches new algo builders. If your strategy needs a live price for 50 instruments, you do not poll the quote endpoint 50 times — you subscribe over the WebSocket feed, which streams ticks without counting against the quote cap. I cover that streaming pattern in depth in my guide to automating Kite Connect with Python. Here is the rate-limit-aware pattern I drop into every client's order module — a simple throttle so you never trip the 10 orders/second wall: import time from kiteconnect import KiteConnect kite KiteConnect(api_key"your_api_key") kite.set_access_token("your_access_token") MIN_GAP 0.12 # ~8 orders/sec, safely under the 10/sec cap _last 0.0 def place(**params): global _last gap time.time() - _last if gap < MIN_GAP: time.sleep(MIN_GAP - gap) _last time.time() return kite.place_order(varietykite.VARIETY_REGULAR, **params) Need a production-grade bot with retry logic, WebSocket reconnection and SEBI-compliant order tagging built in? Message me on WhatsApp at +91 77352 68199 and I'll scope it with you. Zerodha automation & SEBI policy in 2026 The API price is trivial; the compliance layer is where 2026 differs sharply from earlier years. Two rules govern whether your automated setup is legal. 1. Static IP whitelisting (mandatory since 1 April 2025) You must configure a static IP address to place orders via Kite Connect. Order requests from an unregistered IP are rejected outright — this applies to every user placing orders through the API, regardless of how few orders you send. You add up to two static IPs (one mandatory primary, one optional secondary) in the Profile section of your developer console, and both IPv4 and IPv6 are supported. Data endpoints (WebSocket, order book, positions) still work from any IP; only order placement is gated. You may share an IP only with immediate family, and you can change it once per calendar week. A cheap VPS or cloud instance with a fixed IP is the standard way retail traders satisfy this. 2. SEBI's retail algo framework (fully mandatory 1 April 2026) SEBI's retail algorithmic trading framework, first issued in its February 2025 circular and rolled out along a phased "glide path," becomes fully mandatory for all Indian stockbrokers on 1 April 2026. The essentials for an API user: Every algo order must carry an exchange-assigned Algo-ID, and the broker is accountable for every algo running through its platform. Individual retail traders can automate up to 10 orders per second (per segment, per exchange) using their own API key without separately registering the strategy — you just need the static IP. Beyond 10 orders/second, the strategy must be registered with the exchange. Third-party algo providers (SaaS platforms, independent developers selling strategies) must register with the exchanges and partner with a broker; they cannot connect directly to the exchange. Market orders via API require market price protection; an order with protection set to 0 is treated as unprotected and rejected. This includes SL-M orders. Note also that using Kite Publisher (where the end user clicks to confirm each order) does not fall under the algo framework, because the human places the order manually. Fully automated order placement does. If you want the full checklist for staying on the right side of these rules, I wrote a developer's guide on building SEBI-compliant algos in 2026 for Zerodha and Fyers. So what does an algo actually cost in 2026? Add it up for a typical solo trader running one automated strategy: Kite Connect (Connect plan): ₹500/month A cloud VPS with a static IP: roughly ₹400–₹800/month depending on provider Your own development time, or a developer to build and maintain the bot The API is the cheapest line item. The real investment is engineering a bot that respects the rate limits, reconnects cleanly, tags orders correctly, and doesn't silently burn your 5,000-order daily quota on rejected requests. That is exactly the work I do — whether you're on Kite Connect, or want the same reliability on MT4/MT5, see my Pine Script development and MT4/MT5 automation services. Frequently asked questions How much does the Zerodha Kite Connect API cost in 2026? ₹500 per month per API key for the paid Connect plan, which includes both live WebSocket data and historical candle data. The Personal plan is free but has no market data. Startups building mass-retail products can apply for free access. What are the Kite Connect API rate limits? 10 orders/second and 10 requests/second on most endpoints, 3 requests/second for historical candles, and 1 request/second for quotes. Hard caps are 400 orders/minute, 5,000 orders/day and 25 modifications per order. Is automated trading allowed on Zerodha Kite Connect in 2026? Yes. Retail traders can run automated strategies up to 10 orders/second per segment/exchange without registering the strategy, provided they whitelist a static IP. Above that rate, or if you sell your strategy to others, the algo must be registered with the exchange under SEBI's framework, mandatory from 1 April 2026. Do I need a static IP for the Zerodha API? Yes. Since 1 April 2025, a whitelisted static IP is mandatory to place any orders through Kite Connect. Data-only endpoints work from any IP, but order requests from unregistered IPs are rejected. Can I use Kite Connect with Python? Yes. Zerodha maintains the official pykiteconnect library, and Python is the most common language for Kite bots. See my full Kite Connect Python automation guide for the complete setup. Want a rate-limit-safe, SEBI-compliant Kite Connect bot built for your strategy? WhatsApp me at +91 77352 68199. Related guidesAutomating other Indian brokers? See my walkthroughs for Angel One + TradingView webhook automation and the Fyers webhook setup — both cover the same 2026 SEBI static-IP rules. Risk disclaimer: Trading and investing in securities carry substantial risk of loss and are not suitable for every investor. Automated strategies can amplify both gains and losses. Nothing in this article is investment advice or a guarantee of returns. Verify all pricing, rate limits and regulatory requirements directly with Zerodha and SEBI before deploying capital, as these can change. Trade only with money you can afford to lose.

Zerodha Kite Connect API Pricing & Rate Limits (2026)

Jayadev Rana