Use your AlgoIP static IP with any proxy-enabled tool

If your tool or library exposes Host, Port, Username and Password, it works with AlgoIP. Here is the one pattern that covers all of them.

Almost every trading platform, bot framework and HTTP library can route through an authenticated proxy. AlgoIP is a standard HTTP CONNECT and HTTPS proxy on port 443, so the recipe is always the same four values.

Wherever your tool asks for a proxy (the field may be called Host, Server, Proxy IP or Static IP), use the mapping below.

Credential mapping

Open your dashboard at /my-ips and pick the allocation you want to route through. Its card shows everything the four fields need: the proxy Host (your node hostname), your assigned static IPv4 and IPv6, the Port (443), your Username (the user_id value, which is your api_key and starts with aip_live_) and your Password (the password value, which is your api_secret and starts with aip_sec_). The same details are in your provisioning email. Keep the api_secret private, it is the password to your dedicated IP.

• Host = Your node hostname (for example dc46-mum-01.algoip.in) or your assigned static IPv4 / IPv6
• Port = 443
• Username = Your api_key (shown as user_id in /my-ips, starts with aip_live_)
• Password = Your api_secret (shown as password in /my-ips, starts with aip_sec_)

Steps

1. Find the proxy setting in your tool. Look for Proxy, Network or Connection settings. GUIs usually have Host/Server, Port, Username and Password fields. Libraries take a proxy URL like http://user:pass@host:443.
2. Map the four AlgoIP values. Host is your node hostname or static IPv4/IPv6, Port is 443, Username is your api_key (user_id, aip_live_...) and Password is your api_secret (aip_sec_...).
3. Choose hostname or IP. Default to the hostname for full capability. If the field only accepts an IP, paste your static IPv4 or IPv6; it works on the same port and credentials (see the note below).
4. Verify and whitelist. Confirm the egress IP on /check-ip, then whitelist that AlgoIP IPv4 at your broker’s API portal.

Verify the egress IP

• Route a request to https://ip64.algoip.in/all?format=json (or open /check-ip in a proxied browser). The IP must equal your whitelisted AlgoIP IPv4.

Hostname or static IP in the Host field?

Both work, on the same port 443 with the same username and password. The hostname (for example dc46-mum-01.algoip.in) is the default and gives you full capability, because the AlgoIP proxy serves both plain HTTP CONNECT and HTTPS (TLS to the proxy, also called TLS-in-TLS) on that one port.

Many traders instead paste their assigned static IPv4 or IPv6 straight into the Host field. That works everywhere the basic proxy mode is supported. The only thing a raw IP cannot do is TLS-to-the-proxy, because that handshake needs the certificate that matches the hostname. And TLS-in-TLS only matters at all if your tool or library can speak to an HTTPS proxy in the first place, which many GUIs and libraries (Python requests, for one) cannot. So for the large majority of tools, using the IP costs you nothing.

Rule of thumb: hostname = full capability; IP = works everywhere basic proxy mode is supported, just without TLS-in-TLS.

Find your AlgoIP credentials · Check your IP · Get a static IP · All setup guides