A static IP for your exchange API key. Lock it to one address.
Exchanges want trading keys tied to an IP address. Your home internet doesn't keep one. TrueIP gives your bot a dedicated IPv4 in Mumbai that you bind the key to once.
Why your bot's API key keeps breaking.
The bot ran fine for a week. Then one morning every order fails with an IP error, or you find the key can only read balances. Nothing in your code changed. The exchange is checking where the request came from, and the answer moved.
Exchanges push hard on IP binding. On Binance, a key without an IP restriction is limited to reading data, and turning on withdrawals needs an IPv4 restriction. Delta Exchange India won't give trading permission to a key without whitelisted IPs, and WazirX recommends the same. Some exchanges also expire or delete keys that have no IP bound.
Home internet makes this hard. Jio and Airtel broadband addresses change when the router restarts after a power cut, and many connections share an address behind CGNAT. A laptop that moves between home and office Wi-Fi changes address every time it moves.
There's also an IPv6 trap. In our test from Mumbai, api.binance.com didn't answer over IPv6 at all, while Delta Exchange did and accepts IPv6 in its whitelist. A machine with both kinds of address can send some calls out on the one you never whitelisted. One fixed outbound address takes that guesswork away.
Bind the key once. Trade every day.
- 01
Get a dedicated IPv4
Sign up and pay online. The IP is assigned in minutes, with its own host, port, username and password.
- 02
Bind your API key to it
When you create or edit the key, turn on the IP restriction and paste your TrueIP address. Enable only the permissions the bot needs.
- 03
Check the route
Run curl -x http://USER:PASS@HOST:PORT https://ifconfig.co from the bot's machine. It should print the IP you just bound.
One proxy line in your bot.
ccxt has proxy settings on the exchange object: httpsProxy for REST calls and wssProxy for websocket streams. Set them and every call leaves from your fixed IP.
- ✓ Works with ccxt, python-binance or plain REST calls
- ✓ REST and websocket streams through the same IP
- ✓ One IP per bot or per exchange account, if you want them separate
- ✓ Credentials for every IP downloadable as CSV
What a static IP for exchange APIs gives you.
One IPv4, only yours
A whole address reserved for your account and never shared, so no other customer's traffic leaves from the IP your key trusts.
Same IP on renewal
Renew on time and the address doesn't change. You never have to rebuild the key or edit its whitelist.
Your keys stay private
Calls to the exchange are HTTPS end to end. We see encrypted traffic and a destination, never your key, secret or orders.
Per-IP credentials
Each IP has its own host, port, username and password, so a second bot or account gets its own address.
Hosted in Mumbai
The node runs in Mumbai on TrueIP's own routed address range, so your requests come from an Indian IP.
Priced per IP. IPv4 for most exchanges.
Binance asks for an IPv4 address, so IPv4 is the plan for most bots. IPv6 only makes sense on an exchange that accepts it.
IPv4 dedicated
Pick this for BinanceWorks with every exchange in our tests, including the ones that don't answer over IPv6. Same price per month on any term.
- Dedicated IPv4, never shared or rotated
- Per-IP host, port, user and password
- Same IP kept across renewals
- CSV export of credentials
- GST invoice on every payment
IPv6 dedicated
Locked for lifeFor exchanges that accept IPv6 in their whitelist, such as Delta Exchange India. Check yours first.
- Unique /128, never shared or rotated
- Per-IP host, port, user and password
- Same IP kept across renewals
- Price locked while you stay subscribed
Not sure which your exchange takes? Try pasting an address like 2001:db8::1 into its IP field, or use the plan finder.
Exchange API questions.
Will the IP ever change?
No. The address stays the same for your whole term and on every renewal. Renew before it expires and the key's whitelist never needs touching.
Do I get a GST invoice?
Yes, on every payment. IPv4 is ₹200 + 18% GST, so ₹236 a month. Add your GSTIN in the portal if you trade through a company.
Is my data visible to you?
No. Your connection to the exchange is TLS encrypted end to end. We see encrypted traffic and the destination host, not your API key, secret or orders. Breaking TLS would trigger a certificate error, so it can't happen silently.
IPv4 or IPv6 for this?
IPv4 for Binance and most others. Binance asks for an IPv4 address, and its API didn't answer over IPv6 in our test from Mumbai. Delta Exchange India accepts IPv6 in its whitelist, so IPv6 at ₹50 a month works there.
Will websocket streams work too?
Yes. Websockets go through the same proxy. In ccxt, set wssProxy as well as httpsProxy, or your streams will leave from your normal connection.
Can I run several bots?
Yes. Take one IP per bot or per exchange account and bind each key to its own address. There's no cap on how many IPs you can take.
Does this get around exchange or country restrictions?
No, and it isn't meant to. TrueIP gives you a fixed Indian IP to bind your key to. Use it only with exchanges and accounts you're allowed to use, under their terms.
Guides for this setup
How to lock your crypto exchange API key to one IP (and why you should)
Binding your exchange API key to one IP stops a leaked key being used anywhere else. How to do it, which address to use, and how to keep it from changing.Running a trading bot from home: getting a stable IP for exchange APIs
Running a crypto bot on a home PC? Power cuts, router restarts and CGNAT keep changing your IP. How to keep a stable IP for exchange APIs from home.Can a static IP provider see your trades? What TLS actually hides
If your trades route through a provider's static IP, can they read your orders or positions? The short answer is no. Here is exactly why, in plain terms.More setups on the use cases page, or find the right IP type in 30 seconds.
A fixed IP for your API key. Live in minutes.
A dedicated IPv4 from Mumbai for ₹200 + GST a month. Bind your key once and keep the same IP on every renewal.