How to get a static IP for your trading API (step by step)

Short answer: You get a fixed address from a static-IP provider (or as a side effect of a VPS or a static plan from your ISP), then register that single address on your broker's API whitelist. Once it is whitelisted, your bot connects from the same address every session and stops getting locked out. The cheapest, lowest-maintenance route is a dedicated static IP you do not have to manage.

Here is the full process, the options ranked by cost and hassle, and the steps to whitelist it.

Your options, ranked

There are four common ways to get a fixed address. They are not equal.

1. Dedicated static IP from a provider — you get one fixed address, whitelist it, done. Nothing to maintain, lowest cost, often free. Best fit for most algo traders.
2. VPS — a remote server that comes with a static address. Works, but you are paying for a whole machine and managing an OS just to get the IP. Only worth it if you also need to run code 24/7. We break this down in static IP vs VPS for algo trading.
3. Static IP plan from your ISP — some providers sell a fixed address as an add-on. Often expensive, business-tier only, and tied to one physical location.
4. VPN with a dedicated IP — works in theory, but shared or rotating exit nodes break whitelisting, and a "dedicated IP" add-on costs extra and adds a hop.

For most traders who already run their algo on their own machine, option 1 is the right call. The rest are paying for things you did not ask for.

Step by step: getting and whitelisting your static IP

1. Get the fixed address

Sign up for a static IP for algo trading and you receive one dedicated address tied to your account. With TrueIP this is an authenticated proxy endpoint: a host, port, and credentials. Your bot connects to that endpoint over IPv4, and every request to your broker egresses from your dedicated static IP.

2. Note your exact outbound IP

Whitelisting cares about the address your broker sees, which is your outbound (egress) IP, not your local one. Confirm it before you whitelist so you register the correct value. With a dedicated static IP this is fixed and given to you up front.

3. Whitelist it with your broker

Log in to your broker's API or developer console, find the IP whitelist (sometimes under app settings or API security), and add your static address. Save it. Note that some brokers take a few minutes to a few hours to apply the change.

4. Point your bot through the static IP

Configure your trading client or script to route its outbound traffic through the dedicated address (for an authenticated proxy, set the proxy host, port, and credentials in your HTTP client). Now every order leaves from the whitelisted address.

5. Test with a small request

Before going live, fire a low-risk authenticated call (account balance, positions, a tiny test order if your broker has a sandbox). If it succeeds, the whitelist match is working. If it is rejected, double-check the egress IP matches the whitelisted one exactly.

What to avoid

• Dynamic IPs. A home or office connection that rotates its address will keep breaking the whitelist. This is the root cause behind most "my bot randomly stops working" complaints, explained in full in broker API IP whitelisting explained.
• Shared IPs. If other people share your exit address, your broker sees traffic mixed with theirs, and a fixed value is not guaranteed. Whitelisting needs a dedicated address.
• Overpaying for a VPS when all you needed was the address.

What TrueIP offers

TrueIP is the get-the-address-without-the-hassle option. One dedicated, SEBI compliant IPv6 address per account, hosted in Mumbai for low latency to Indian exchanges, delivered as a ready-to-use authenticated proxy endpoint. You whitelist it once and never manage a server. Free while we grow the network, with IPv4 available at cost for brokers that require it.

---

Ready to set yours up? Get a free static IP here.