Does Zerodha officially require IP whitelisting?

Kite Connect does not force a whitelist for all users, but its security layer monitors origin IP consistency, and SEBI's algo framework is pushing all brokers toward registered static endpoints. A fixed IP prevents session invalidation today and keeps you compliant tomorrow.

Which plan do I need for one Zerodha account?

A single IPv4 dedicated proxy (₹200/month) is enough for one broker API. The IP supports both REST and WebSocket traffic.

Static IP Zerodha: Kite Connect API Whitelisting Guide (2026)

Static IP Zerodha guide — Kite Connect whitelisting, Python proxy setup, API key flow and dedicated Mumbai IP for zerodha algo trading without session drops.

Static IP Zerodha setup means one dedicated IPv4 (or IPv6 if the portal accepts it) pasted into Kite Connect IP whitelist, then all kiteconnect and KiteTicker traffic exits that address via HTTP proxy port 443.

Why Kite Connect users need a fixed IP

Zerodha's Kite Connect API authenticates with an API key, API secret and a daily access token. When your requests suddenly arrive from a new IP — because your broadband rotated — Zerodha's security layer can invalidate the session or flag the account. Traders running Python bots on home connections see random "TokenException" and connection resets for exactly this reason.

Step 1 — Get a dedicated static Indian IP

Sign up at algo-ip.in, complete the quick KYC (Aadhaar + PAN, mandated for SEBI-compliant provisioning), top up your wallet and allocate an IPv4 static IP (₹200/month). You receive a proxy hostname, HTTP and SOCKS5 ports, a username and a password. The IP is exclusively yours.

Step 2 — Route your Kite Connect session through the IP

In Python, attach the proxy to your KiteConnect session so every REST call exits from your static IP:

Step 3 — Keep the WebSocket ticker on the same IP

For KiteTicker (live market data), route the WebSocket through the same proxy so both REST and streaming traffic share one origin IP. Most Python WebSocket clients accept an http_proxy_host / http_proxy_port parameter, or you can export HTTPS_PROXY in the bot's environment.

Step 4 — Verify your exit IP before market open

Common errors this setup fixes

TokenException: Invalid session — caused by IP change mid-session.
Connection reset / read timeout at 9:15 AM — ISP CGNAT congestion, avoided by datacenter routing.
Login OTP loops when your bot logs in from a "new device/location" every day.

With a dedicated Mumbai IP your bot presents one stable identity to Zerodha every single day — the same address, the same session behaviour, no surprises.