How to set up a static IP / proxy in MyAlgoMate with AlgoIP

Route your MyAlgoMate trading through your dedicated, broker-whitelisted AlgoIP static IP in a few minutes.

MyAlgoMate has a built-in Static IP / Proxy Settings panel, so you do not need any extra software to route your trading through a dedicated IP. You point it at your AlgoIP proxy with four values: Host, Port, Username and Password.

A dedicated static IP is what lets you satisfy your broker’s IP-whitelisting requirement. You whitelist one fixed AlgoIP address on your broker’s API portal, then tell MyAlgoMate to send its API traffic out through that same address.

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.

Steps

  1. Open Static IP / Proxy Settings in MyAlgoMate. In MyAlgoMate, open the Static IP / Proxy Settings panel (it sits with your account and connection settings). This is where MyAlgoMate keeps the four proxy fields.
  2. Tick "Enable Static IP / Proxy". Turn on the Enable Static IP / Proxy checkbox so MyAlgoMate routes outbound API calls through the proxy instead of your local connection.
  3. Fill in your AlgoIP details. Copy the four values from your /my-ips card: Host is your node hostname (or your static IPv4/IPv6), Port is 443, Username is your api_key (the user_id value, aip_live_...) and Password is your api_secret (aip_sec_...).
  4. Press Test, then Save. Click MyAlgoMate’s Test button. A success (Proxy Valid, 200 OK, with the served IP) means MyAlgoMate reached your broker through your dedicated IP. Save the settings.

Verify it with the Test button

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