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 the proxy and a credential to the web cmdlets: Invoke-RestMethod https://api.ipify.org -Proxy http://HOST:PORT -ProxyCredential $cred, where $cred is a PSCredential with your username and password. Invoke-WebRequest takes the same parameters, in both Windows PowerShell 5.1 and PowerShell 7.
PowerShell is how many Windows admins and automation scripts call web APIs. The two editions find proxies differently: Windows PowerShell 5.1 follows the Windows proxy settings, while PowerShell 7 reads HTTP_PROXY, HTTPS_PROXY and NO_PROXY first. Passing -Proxy explicitly behaves the same in both.
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.
$PSVersionTable.PSVersion.Both products use the same setup in PowerShell. What changes is how long an IP stays with you.
An ISP line is one dedicated US IP for the whole month, so a -WebSession object plus the same ISP proxy on every call keeps an account's cookies and IP together. SOCKS5 on ISP lines works in PowerShell 7.2 and later.
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.
Each new connection through a rotating line can get a new residential IP, but calls in the same web session can reuse a connection. Use a sticky line when a script must stay on one IP for its whole run, and separate calls without -WebSession when you want rotation.
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.
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 PowerShell.
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.
Run $PSVersionTable.PSVersion. 5.1 is Windows PowerShell; 7.x is PowerShell (pwsh).
Build a PSCredential from your username and password, or run Get-Credential to type them in a prompt.
Add -Proxy http://HOST:PORT -ProxyCredential $cred to Invoke-WebRequest or Invoke-RestMethod.
Call https://api.ipify.org with and without the proxy; the two addresses should differ.
Replace the highlighted placeholders with the values from your dashboard. Pick an example to see its code.
$secure = ConvertTo-SecureString "PASSWORD" -AsPlainText -Force
$cred = [pscredential]::new("USERNAME", $secure)
$params = @{
Uri = "https://api.ipify.org?format=json"
Proxy = "http://HOST:PORT"
ProxyCredential = $cred
TimeoutSec = 30
}
(Invoke-RestMethod @params).ipInvoke-RestMethod "https://api.ipify.org" -Proxy "socks5://HOST:PORT" -ProxyCredential $credhttp://HOST:PORT for HTTPS sites too: the request is tunnelled with CONNECT and TLS runs end to end. SOCKS5 is available on static ISP and ISP subnet proxies (switched on per list in the dashboard, same credentials) and relies on the .NET SOCKS client in PowerShell 7. -ProxyUseDefaultCredentials sends your Windows sign-in to a corporate proxy; CleanProxies needs -ProxyCredential instead.# Windows: save for your user, then open a new pwsh window
[Environment]::SetEnvironmentVariable("HTTP_PROXY", "http://USERNAME:PASSWORD@HOST:PORT", "User")
[Environment]::SetEnvironmentVariable("HTTPS_PROXY", "http://USERNAME:PASSWORD@HOST:PORT", "User")
# in the new window:
Invoke-RestMethod https://api.ipify.org
Invoke-RestMethod https://api.ipify.org -NoProxy # skip the proxy for one call$proxy = New-Object System.Net.WebProxy("http://HOST:PORT")
$proxy.Credentials = New-Object System.Net.NetworkCredential("USERNAME", "PASSWORD")
[System.Net.WebRequest]::DefaultWebProxy = $proxy
Invoke-RestMethod https://api.ipify.orgpwsh (on macOS and Linux, export them in the shell that launches it). -NoProxy arrived in PowerShell 6; Windows PowerShell 5.1 doesn't have it and reads the Windows proxy settings unless you set DefaultWebProxy as shown.-SessionVariable saves cookies and headers in a session object; reuse it with -WebSession and pass the same ISP proxy on every call so the account never changes IP.
$p = @{ Proxy = "http://HOST:PORT"; ProxyCredential = $cred }
Invoke-RestMethod "https://example.com/login" -Method Post -Body @{ email = "me@example.com" } -SessionVariable shop @p | Out-Null
Invoke-RestMethod "https://example.com/account" -WebSession $shop @pInvoke-RestMethod https://api.ipify.org -Proxy "http://HOST:PORT" -ProxyCredential $cred
Invoke-RestMethod https://api.ipify.org -NoProxyThe first line prints the proxy's exit IP and the second your own. In Windows PowerShell 5.1, drop -NoProxy and run the second line with no default proxy set.
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).
-ProxyCredential is missing, or the username or password is wrong.Rebuild $cred from the dashboard line and pass it with -ProxyCredential on every call.-NoProxy.Drop the switch, or run the script in PowerShell 7 (pwsh).-Proxy explicitly, or set the variables first and start a new pwsh.[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 first, or use PowerShell 7.Setup guides and best practices from the CleanProxies blog.
Setup guides for tools people run next to PowerShell.
Manual proxy setup in Settings, exceptions, proxy logins, PowerShell and netsh winhttp.
Setup guideWebProxy with NetworkCredential, SOCKS5 in .NET 6+, and named clients per proxy with IHttpClientFactory.
Setup guideThe -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 guideStraight answers about running CleanProxies in PowerShell.
Add -Proxy with the proxy address and -ProxyCredential with a PSCredential holding your CleanProxies username and password. Invoke-RestMethod accepts the same two parameters.