An active CleanProxies plan
Static ISP proxies for fixed US IPs, or rotating residential / mobile proxies for pools. The $4.99 trial works too.
Pass --proxy once per URL scheme: http --proxy=http:http://USERNAME:PASSWORD@HOST:PORT --proxy=https:http://USERNAME:PASSWORD@HOST:PORT https://api.ipify.org. HTTPie also reads HTTP_PROXY, HTTPS_PROXY and ALL_PROXY, and accepts socks5h:// proxy URLs for SOCKS5 on static ISP proxies.
HTTPie is a friendlier cURL for testing APIs and reading responses. It runs on Python Requests, so its proxies follow Requests rules: one mapping per scheme of the URL you call, with the proxy URL after the colon. The usual mistake is mapping only http:, which sends HTTPS calls out directly.
Static ISP proxies for fixed US IPs, or rotating residential / mobile proxies for pools. The $4.99 trial works too.
From the dashboard's proxy manager: host (or IP), port, username and password. Convert lists with the proxy list formatter.
pip install httpie, brew install httpie or your package manager); check with http --version.requests[socks] dependency. If an install left it out, run pip install -U "requests[socks]" in HTTPie's environment.Both products use the same setup in HTTPie. What changes is how long an IP stays with you.
HTTPie opens a new connection on every run, so a rotating line normally returns a different residential IP each time; run the IP check twice to see it change. Use a sticky line to keep one IP across a short series of calls.
Residential IPs in 190+ countries with country, state and city targeting. Rotate on every request or hold a sticky session for up to 90 minutes; GB never expire.
An ISP line is one dedicated US IP, so a named HTTPie session plus the same ISP proxy on every call gives an account one stable address and one cookie jar. SOCKS5 works on these lines too.
Dedicated static IPs registered to US and Canadian ISPs. The address stays the same for as long as you hold it, with unlimited bandwidth and HTTP(S) or SOCKS5 access.
Every product connects over HTTP(S); static ISP and ISP subnet proxies also run SOCKS5 and IP whitelisting. This is what the dashboard gives you to paste into HTTPie.
IP:PORT:USER:PASSOne line per dedicated IP. With IP whitelisting on, the line is just IP:PORT and no password is sent.
HOST:PORT:USER:PASSGenerated in the proxy manager. The username carries the location and session you pick, so generate a new list to change them.
http://USERNAME:PASSWORD@HOST:PORTsocks5://USERNAME:PASSWORD@HOST:PORTUse http:// even for HTTPS websites; the TLS session still runs end to end. The socks5:// form is for static ISP and ISP subnet proxies.
Four steps, then check the exit IP with the free proxy checker.
Install the CLI and run http --version to confirm it works.
Turn your dashboard line into http://USERNAME:PASSWORD@HOST:PORT.
Add --proxy=http:URL and --proxy=https:URL. The part before the first colon is the scheme of the website you call.
Call https://api.ipify.org with --body; the output is your exit IP.
Replace the highlighted placeholders with the values from your dashboard. Pick an example to see its code.
http --proxy=http:http://USERNAME:PASSWORD@HOST:PORT \
--proxy=https:http://USERNAME:PASSWORD@HOST:PORT \
https://api.ipify.org format==jsonhttp --proxy=http:socks5h://USERNAME:PASSWORD@HOST:PORT \
--proxy=https:socks5h://USERNAME:PASSWORD@HOST:PORT \
https://api.ipify.orgformat==json is HTTPie syntax for a query parameter. Percent-encode @ or : in a password (@ becomes %40). SOCKS5 is switched on per ISP proxy list in your dashboard and uses the same username and password.export HTTP_PROXY="http://USERNAME:PASSWORD@HOST:PORT"
export HTTPS_PROXY="http://USERNAME:PASSWORD@HOST:PORT"
export NO_PROXY="localhost,127.0.0.1"
http --body https://api.ipify.orgproxy="https:http://USERNAME:PASSWORD@HOST:PORT"
http --session=shop --proxy="$proxy" POST https://example.com/login email=me@example.com password=secret
http --session=shop --proxy="$proxy" https://example.com/account--proxy on every call (or export the variables) to keep the account on one IP.{
"default_options": [
"--proxy=http:http://USERNAME:PASSWORD@HOST:PORT",
"--proxy=https:http://USERNAME:PASSWORD@HOST:PORT"
]
}~/.config/httpie/config.json; on Windows it's %APPDATA%\httpie\config.json. HTTPIE_CONFIG_DIR moves it.http --body --proxy=https:http://USERNAME:PASSWORD@HOST:PORT https://api.ipify.org--body prints only the response, so the command below prints the exit IP. Run it again without --proxy (and with no proxy variables set) to compare with your own address.
Open What is my IP? through the proxy to see the address and headers a website receives, or paste up to ten lines into the free proxy checker to test connectivity, latency and exit IP.
Still stuck? Our 24/7 support team answers fast: contact us with the error and the line you used (leave the password out).
--proxy=http:... is set.Add --proxy=https:http://USERNAME:PASSWORD@HOST:PORT.https://.Use http:// for the proxy itself; HTTPS sites still tunnel securely.pip install -U "requests[socks]" there (with pipx: pipx inject httpie pysocks).Setup guides and best practices from the CleanProxies blog.
Setup guides for tools people run next to HTTPie.
The -x flag, separate credentials, socks5h for remote DNS, env vars and a loop to test a whole list.
Setup guideThe proxies dict, Session-level proxies, SOCKS5 with remote DNS and rotation over an ISP list.
Setup guideCustom proxy configuration, Proxy auth, Proxy bypass, and the difference from Postman's capture proxy.
Setup guideEnable proxy, Proxy for HTTP and HTTPS with user:pass in the URL, No proxy and per-request opt-out.
Setup guideStraight answers about running CleanProxies in HTTPie.
The first part is the scheme of the website you request, the rest is the proxy URL. https:http://HOST:PORT means requests to https sites go through an HTTP proxy, which is the normal setup for CleanProxies.