Zerodha Static IP

Kite Connect static IP requirement

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

Kite Connect does not require a static IP for standard retail / developer use. The API is accessible from any IP that’s authorised via the OAuth login flow.

When static IP matters

For specific use cases:

  • High-frequency institutional access: Some plans may require IP whitelisting for security.
  • Specific compliance scenarios: Particular SEBI / exchange requirements.
  • Custom enterprise setups: Negotiated configurations.

For retail / developer use, dynamic IPs work fine.

How authentication works

Authentication is via OAuth + access token, not IP-based. The same login can come from different IPs.

For details: Kite Connect OAuth login flow .

See also

External references

References

  1. Zerodha, Kite Connect technical specifications, 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.