Static IP for CoinDCX API keys
CoinDCX made IP binding mandatory: old API keys are deprecated and every new key must be locked to the IP your bot trades from. Requests from any other IP are rejected. On home broadband or mobile data that IP changes, and the key stops working. A dedicated Algo-IP Mumbai IPv4 stays fixed, so you bind it once.
CoinDCX API facts
- API: CoinDCX Exchange API
- Portal: coindcx.com → Profile → API Dashboard
- Whitelist: API Dashboard → Create A New One → bind IP address (mandatory)
- IPv4: yes
- IPv6: confirm in portal
- Max IPs: Confirm in the API key form; create one key per bot or machine
- Protocols: HTTP proxy, REST, Socket.IO WebSocket
- Published: 2026-09-22
- Last verified: 2026-09-27
- Next review: 2026-12-27
- Verification source: CoinDCX security announcement on mandatory IP binding and the CoinDCX API reference (docs.coindcx.com). IPv6 and max-IP limits: confirm in the live key form.
How to whitelist a static IP
- Create an Algo-IP account, finish KYC, allocate IPv4 (₹199/month on a 12-month term).
- Copy the dedicated IPv4 from the dashboard.
- On coindcx.com open Profile → API Dashboard. Delete any old key — CoinDCX has no regenerate option.
- Click Create A New One, enter a label, and bind the dedicated IPv4. If the form binds your current browser IP instead of letting you type one, open coindcx.com through the Algo-IP proxy before creating the key.
- Enter the email and SMS OTPs, click Create, and store the API secret immediately — CoinDCX shows it only once.
- Route every REST call to api.coindcx.com and the stream-spot.coindcx.com socket through HOST:443, then confirm api.ipify.org through the proxy matches the bound IP.
REST setup
All signed REST calls (balances, orders, trades) go to https://api.coindcx.com and are checked against the bound IP. Set HTTPS_PROXY=http://USER:PASS@HOST:443 in the bot process, or pass the proxy to every requests/axios client.
WebSocket setup
CoinDCX streams use Socket.IO at https://stream-spot.coindcx.com. Socket.IO opens its own connection, so give that client the same HTTP CONNECT proxy. If REST works but private channels fail, the socket left from the machine IP.
Python / proxy hint
REST: requests.Session() with proxies={"https": "http://USER:PASS@HOST:443"} for api.coindcx.com (X-AUTH-APIKEY / X-AUTH-SIGNATURE headers).
WebSocket: python-socketio connects to https://stream-spot.coindcx.com — pass the same proxy to its HTTP session so the socket does not bypass it.
Common errors
CoinDCX API stopped working after the security update
Keys created before mandatory IP binding are deprecated. Delete the old key and create a new one bound to your dedicated Algo-IP IPv4.
CoinDCX rejects requests from a bound key
The request left from a different IP than the one bound to the key. Check api.ipify.org through the proxy and make sure REST and the socket both use HOST:443.
Can I use one CoinDCX key on several machines?
Yes, if every machine sends traffic through the same Algo-IP proxy. The exchange only sees the dedicated IPv4, not each machine.
IPv6 is ₹99/month only when an IPv4 VPS already has a free IPv6 and this broker’s form accepts an IPv6 literal. IPv4 is ₹199/month on a 12-month term.
Related guide: broker-ip-address-whitelisting-india. Also see dedicated IPv4, trading proxy, broker setup wizard and all brokers.
Other broker setups