How-to
Rate limit
Errors
How to fix 'max order request exceeded' without 5000 orders
The “max order request exceeded” error in Kite Connect typically indicates you’ve hit the per-second or per-minute rate limit, not the daily 5000-order cap.
Conflict-of-interest disclosure. This guide is published by WebNotes Editorial Team for informational purposes. WebNotes has no commercial relationship with Zerodha. No affiliate commission is earned from successful completion of the procedure.
Step-by-step procedure
Four steps per the procedure infobox.
Rate limits
Per Kite Connect rate limits :
- Per second: ~3 orders.
- Per minute: ~200 orders.
- Per day: 5000 orders.
Burst order placement hits the per-second limit first.
See also
- Kite Connect rate limits
- Kite Connect (Zerodha API)
- Kite Connect API pricing
- Kite Connect FAQs
- Algo trading with Kite Connect
- Kite Connect OAuth login flow
- Sign up and get Kite API key
- Kite Connect access token generation
- pykiteconnect Python quickstart
- kiteconnect.js Node.js quickstart
- Kite Connect Java SDK
- Place order via Kite Connect (Python)
- Kite Connect order modify / cancel
- Kite Connect basket orders API
- Kite Connect GTT API
- Kite Connect historical data API
- Kite Ticker WebSocket (Python)
- Backtesting with Kite historical API
- Kite Connect sandbox / mock
- Mobile browser issue with Kite Connect login
- Will Zerodha help code strategies
- Use Kite API data on other platforms
- Historical API without Kite Connect access
- Net vs Day in positions API
- Historical vs live data pricing
- Kite API charges and plans
- Kite Connect static IP requirement
- Kite Publisher API
- Kite MCP for AI assistants
- Zerodha Open API community
- Algorithmic trading in India
- Zerodha
- Kite (Zerodha)
External references
References
- Zerodha, Kite Connect rate limits, kite.trade.