Kite Connect: "IP address is already linked to another account"
When you add an IP in the Kite Connect developer console and it's already registered to another Zerodha developer account, the console refuses it. Users report the message as "The IP address(es) you are trying to add are already linked to another account. Each IP address can only be linked to one account." Here's why it happens and what to do.
Why Zerodha refuses the IP
Under SEBI's algo trading rules, a static IP is tied to one client so every API order can be traced to the person behind it. Zerodha applies this across all its developer accounts: once an IP is on one account's whitelist, another account can't add it. Zerodha also warns that sharing an IP outside your immediate family can lead to suspension of the Kite Connect account.
Common reasons you see it
- A family member registered it on their own developer account. Two people in one house on one broadband connection share one public IP. Family sharing is allowed for spouse, dependent children and dependent parents, but not through two separate developer accounts (see the fix below).
- The IP isn't really yours alone. Shared proxy pools, VPN exits, office networks and CGNAT home connections put many people behind one address. Someone else may have registered it.
- The address was used before you. Cloud servers and ISP static IPs get reassigned. A previous holder of the address may still have it on their whitelist.
- A second developer account of your own. The IP is already on your other developer account.
How to fix it
- Check who else uses the address. If the connection is shared, the IP isn't one you can register by yourself.
- If it's family, use one developer account. Zerodha's team explains on the Kite forum that the static IP is set at the developer account level, and that one developer account can hold several apps, each created with a different client ID: one for you, one for your spouse, and so on for dependent children and parents. Each app gets its own API key and secret, and all of them use the account's IP whitelist. Sharing this way is a declaration that the accounts belong to family.
- If you're sure the IP is only yours, raise a ticket on Zerodha's support portal and ask them to check where it's mapped. That's what Zerodha's team told a user in this situation on the Kite forum.
- If you need to trade today, use a different IP that only you use. A dedicated static IP that's never been handed to anyone else avoids the problem. Zerodha accepts IPv4 and IPv6.
Remember that you can change your Kite whitelist only once a calendar week, so check the new address before you save it: curl -x http://USER:PASS@HOST:PORT https://ifconfig.co. Setup details are on static IP for Zerodha Kite Connect.
FAQs
Can my wife and I use the same static IP on Zerodha?
Yes. Create a separate app for each of you under one Kite Connect developer account, each with its own client ID. The IP whitelist is set on the developer account, so both apps use it. Zerodha warns that sharing outside immediate family can get API access suspended.
Does an HUF count as family?
When asked on the Kite forum, Zerodha's team pointed to the exchange circular rather than giving a yes or no, so ask Zerodha support for your case.
Why does a brand new static IP show as already linked?
It may have been someone else's before it was assigned to you, or it may be shared behind the scenes. Ask Zerodha support to check, or use an IP that's dedicated to you.
Sources
- Zerodha support: static IP for Kite Connect
- Kite Connect forum: "IP already linked to another account"
- Kite Connect forum: sharing a static IP with family through apps under one developer account
- Z-Connect: NSE's retail algo trading framework
Get your dedicated static IP
IPv6 ₹50 a month, IPv4 ₹200 a month, plus GST. Live in minutes, whitelisted once.