Zerodha
Static IP
Kite Connect static IP requirement
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
- Kite Connect (Zerodha API)
- Kite Connect API pricing
- Kite Connect FAQs
- Sign up and get Kite API key
- Kite Connect access token generation
- Kite Connect OAuth login flow
- Algo trading with Kite Connect
- How to fix max order request exceeded without 5000 orders
- Will Zerodha help code strategies
- Use Kite API data on other platforms
- Historical API without Kite Connect access
- How to get invoice for Kite Connect subscription
- Kite Connect sandbox / mock
- Mobile browser issue with Kite Connect login
- Net vs Day in positions API
- Historical vs live data pricing
- Kite API charges and plans
- Kite Connect rate limits
- Deactivate / unsubscribe Kite Connect
- pykiteconnect Python quickstart
- kiteconnect.js Node.js quickstart
- Kite Connect Java SDK
- Kite Publisher API
- Kite MCP for AI assistants
- Place order via Kite Connect (Python)
- Kite Connect order modify / cancel
- Kite Connect basket orders API
- Kite Connect GTT API
- Kite Connect historical data API
- Kite Ticker WebSocket (Python)
- Backtesting with Kite historical API
- Zerodha Open API community
- Algorithmic trading in India
- Zerodha
- Kite (Zerodha)
External references
References
- Zerodha, Kite Connect technical specifications, kite.trade.