How-to Rate limit Errors

How to fix 'max order request exceeded' without 5000 orders

From WebNotes, a public knowledge base. Last updated 19 June 2026. Reading time ~2 min.

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 the WebNotes Editorial Team for informational purposes and is written independently. WebNotes operates a Zerodha account-opening referral programme, disclosed on the pages that carry the referral link; this guide does not carry it and earns no referral commission from the procedure described here.

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.

External references

References

Zerodha, Kite Connect rate limits, kite.trade.

Reviewed and published by

WebNotes Editorial Team

The WebNotes Editorial Team covers Indian capital markets, payments infrastructure and retail investor procedures. Every article is fact-checked against primary sources, principally SEBI circulars and master directions, NPCI specifications and the official support documentation published by the intermediary in question. Drafts go through a second-pair-of-eyes review and a separate compliance read before publication, and revisions are tracked against the SEBI and NPCI rule changes referenced in the methodology section.

Last reviewed: 19 June 2026
Conflicts of interest: WebNotes is independent. No relationship with any broker, registrar or bank named in this article.

Cause	Per-minute or per-second rate limit hit
Fix	Throttle requests; check rate limits