Postman & Insomnia — Docs

Postman — global proxy

Open Settings (⌘, / Ctrl+,) → Proxy tab. Disable Use system proxy and enable Add a custom proxy configuration. Fill in:

Proxy type: HTTP
Proxy server: gw.justproxies.online
Port: 8080
Proxy auth: check This proxy requires authentication, then fill in your Username and Password.

The global proxy applies to all collections and environments. If you switch between proxied and direct traffic frequently, keep two Postman workspaces — one with the proxy configured, one without.

Postman — proxy auth

Postman stores the proxy username and password in its settings and injects a Proxy-Authorization header automatically. You don't need to set any headers manually in your requests.

To use sticky sessions, append the session token to the username directly in the proxy settings field:

Proxy username fieldshell

# Rotating (default — new IP per request)
USER

# Sticky — same IP for the whole Postman session
USER-session-postman01

Change the token whenever you want a fresh IP. The password field stays the same.

Insomnia

Open Preferences (⌘, / Ctrl+,) → HTTP section → HTTP Proxy. Enter the full proxy URL including credentials:

Insomnia — HTTP Proxy fieldshell

http://USER:[email protected]:8080

Set the same value in the HTTPS Proxy field. Leave No Proxy blank unless you want certain hosts to bypass the proxy.

Insomnia also supports the HTTP_PROXY and HTTPS_PROXY environment variables at process launch if you prefer to keep credentials out of the UI.

HTTPS and certificate warnings

Our proxy tunnels HTTPS via CONNECT — we never terminate or inspect TLS. Certificate warnings you see in Postman or Insomnia for HTTPS targets are target-side issues unrelated to the proxy.

If you see an SSL certificate verification failed error for a target that should have a valid cert, check whether the target uses a non-standard CA or a self-signed cert for its staging environment.

Don't disable SSL verification globally just to get rid of a warning — you'll silently miss real certificate problems. Disable it per-request in Postman via the request's Settings tab if you need to test a specific host with a bad cert.

Verifying the proxy is active

Send a request to https://api.ipify.org or https://ipinfo.io/json with the proxy active. The response should show an IP different from your machine's public IP, from the pool you ordered.

Quick check — send this request in Postmanshell

GET https://ipinfo.io/json

# Expected response body (example):
{
  "ip":       "185.220.101.x",
  "city":     "Frankfurt",
  "country":  "DE",
  ...
}

The X-Proxy-Exit-Country and X-Proxy-Pool headers in the response also confirm which pool and country the request exited through. Look for them in Postman's Headers tab of the response.