Point Stoxxo’s per-user Manual Proxy at your dedicated AlgoIP IP so every order egresses from your broker-whitelisted address.
Stoxxo (by AlgoBaba) lets you attach a proxy per user from User Settings. You open the Proxy field, choose Manual Proxy, and enter the same four values AlgoIP gives you.
Stoxxo labels the fields Proxy IP, Port, User and Pwd. Despite the "Proxy IP" label, you can put either your node hostname or your assigned static IP there. Both work on port 443.
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.
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