Static IP for Zerodha Kite Connect

Kite Connect rejects API orders that do not come from the IPv4 you saved on the app. A home or office address changes. A dedicated Algo-IP Mumbai IPv4 stays on the whitelist.

Zerodha API facts

• API: Kite Connect
• Portal: developers.kite.trade
• Whitelist: My Apps → your app → IP Whitelist
• IPv4: yes
• IPv6: confirm in portal
• Max IPs: Confirm in Kite Connect app settings (often one primary IP)
• Protocols: HTTP proxy, REST, KiteTicker WebSocket
• Last verified: 2026-09-22

How to whitelist a static IP

1. Create an Algo-IP account, finish KYC, allocate IPv4 (₹200/month).
2. Copy the dedicated IPv4 from the dashboard.
3. Open developers.kite.trade → My Apps → IP Whitelist and paste that address.
4. Point kiteconnect and KiteTicker at HTTP proxy host + port 443 with your credentials.
5. Call api.ipify.org through the proxy and confirm it matches the Kite whitelist before you generate a token.

Python / proxy hint

Set HTTPS_PROXY / HTTP_PROXY to http://USER:PASS@HOST:443 before KiteConnect().

Common errors

Zerodha API IP not whitelisted

The request left from a different public IP than the one saved on the Kite app. Confirm api.ipify.org through the proxy, then re-check the whitelist field.

Kite 403 after a working session

Home/office IP rotated, or the bot skipped the proxy. Keep every REST and WebSocket call on the same dedicated IP.

Related guide: zerodha-kite-api-static-ip-whitelisting. Also see dedicated IPv4, trading proxy and all brokers.

Other broker setups

• Angel One SmartAPI Static IP
• Dhan API Static IP
• Fyers API Static IP
• Upstox API Static IP
• Static IP for Groww API
• Static IP for 5Paisa API
• Static IP for Alice Blue ANT API
• Static IP for Shoonya (Finvasia) API
• Static IP for Kotak Neo API
• Static IP for mStock (Mirae) API
• Static IP for Goodwill API
• Static IP for ICICI Direct Breeze API
• Static IP for HDFC Sky API