Zerodha Rate limits

Kite Connect rate limits

From WebNotes, a public knowledge base. Last updated . Reading time ~3 min.

Kite Connect rate limits govern how frequently your API can call endpoints:

Endpoint typeApproximate limit
Orders (place / modify / cancel)~3 per second; ~200 per minute; 5000 per day
Quote (live)Higher per-second limit
Historical dataLower (paid; specific limits)
Portfolio / positionsModerate

Design considerations

To avoid hitting limits:

  • Throttle: 200ms-500ms between order placements.
  • Batch where possible: Basket orders for multi-leg strategies.
  • Cache where possible: Don’t re-query positions every tick.
  • Use WebSocket: For live data, avoid polling REST endpoints.

When you hit a limit

Error response: “max order request exceeded” or “rate limit exceeded” (429).

Resolve by:

  • Waiting (typically resets at next minute).
  • Throttling subsequent calls.
  • Implementing exponential backoff.

For details: How to fix max order request exceeded without 5000 orders .

See also

External references

References

  1. Zerodha, Kite Connect rate limits, kite.trade.

Reviewed and published by

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
Conflicts of interest
WebNotes is independent. No relationship with any broker, registrar or bank named in this article.