Postman proxy settings: send API requests through a static IP, then do the same in Newman

Postman proxy settings for your API requests live under Settings > Proxy: turn on Use custom proxy configuration, pick HTTP, enter the host and HTTP port from your ProxyHive order, turn on Proxy auth and add the username and password. Send GET https://api.ipify.org?format=json and the response shows the IP you bought. Newman ignores those settings and reads HTTPS_PROXY from the environment.

App steps checked against Postman's proxy documentation on 2026-09-30. The Newman commands ran the same day with Newman 6.2.2 on Node 22 against a local proxy that enforces a username and password.

#Why test an API through a proxy

• Geo-dependent APIs. Pricing, catalogue and content APIs often answer differently by country. An ISP IP chosen by country, region, city and carrier shows you what a caller in that market gets.
• IP allowlists. Partner APIs that only accept known addresses need a fixed source IP. A static ISP or datacenter IP stays the same for the term you buy, so you can hand it to the partner once.
• Reproducing a scraper's view. Before you wire an endpoint into a scraper, confirm in Postman that the proxy gets a 200 and not a 403.

#Before you start

1. Buy an IP (one is enough) and open the order in the dashboard at https://app.proxyhive.io.
2. Copy HOST, the HTTP port, USERNAME and PASSWORD. Each ISP or datacenter IP is its own endpoint.
3. Use the HTTP port: https:// requests stay encrypted inside the tunnel. HTTP vs SOCKS5 proxies explains when SOCKS5 is worth it.

#Postman proxy settings in the desktop app

Postman's Proxy tab has two different things on it, and mixing them up is the most common mistake:

#1. Open the Proxy tab

Click the Settings icon in the header, select Settings, then open the Proxy tab.

#2. Add a custom proxy

Under the proxy configurations for sending requests:

1. Turn on Use custom proxy configuration.
2. Under Use proxy for, leave both HTTP and HTTPS selected.
3. Under Proxy server, choose HTTP, then enter HOST and the HTTP port.

#3. Add authentication

Turn on Proxy auth and enter the Username and Password from your order. If your order uses an IP allowlist instead, leave it off: the proxy recognises your public IP. Password or IP allowlist covers the trade-off.

#4. Set a bypass list

Proxy bypass takes a comma-separated list of hosts that should skip the proxy. Add localhost and any internal API hosts so local development does not go out through a server in another country.

#The Postman web app

The web app cannot set the default proxy. Postman's docs say to use the system proxy or a custom proxy for sending requests there instead.

#Verify the exit IP

1. Create a request: GET https://api.ipify.org?format=json.
2. Click Send.
3. The ip in the response body should be the address on your order. If it is your own IP, the custom proxy is off or the host is on the bypass list.

To make the check repeatable, add this as the request's post-response script (the Scripts tab in current versions, Tests in older ones):

pm.test("status is 200", () => pm.response.to.have.status(200));
console.log("exit IP", pm.response.json().ip);

#Newman and the Postman CLI with a proxy

Newman does not read the app's settings. It follows the standard HTTP_PROXY, HTTPS_PROXY and NO_PROXY variables, as its README describes, so credentials go into the proxy URL. Export a collection, install Newman first, then run:

npm install -g newman
export HTTPS_PROXY="http://${PROXY_USER}:${PROXY_PASS}@${PROXY_HOST}:${PROXY_PORT}"
export NO_PROXY="localhost,127.0.0.1"
newman run ip-check.postman_collection.json

Our run through the local test proxy printed:

→ Exit IP
  GET https://api.ipify.org?format=json [200 OK, 243B, 165ms]
  ✓  status is 200
  ┌
  │ 'exit IP', '78.61.58.198'
  └

The IP there is our test machine's, because the local proxy exits from it; through a ProxyHive IP you see that IP instead. Two things we hit:

• Install before you export. npx newman with HTTPS_PROXY set sends npm's own registry download through the proxy too. Without credentials in the URL, npm stopped with E407 Proxy Authentication Required.
• A proxy challenge crashed Newman 6.2.2. With no credentials in the URL, the run did not report a 407; it died with Error: Unknown object type "asyncfunction". If you see that, check the proxy URL before anything else.

NO_PROXY behaved as expected: listing api.ipify.org sent that request direct. The Postman CLI (postman collection run) is a separate tool; check its own docs before assuming it reads the same variables.

#Troubleshooting

• 407 Proxy Authentication Required. Wrong username or password, or the order is on IP allowlist and your current IP is not on it.
• "Could not send request" or a connection error. Wrong host or port, or a SOCKS5 port entered as HTTP.
• The IP check shows your own address. You edited the default proxy, not the custom one, or the target host is in the bypass list.
• Some requests go direct, others through the proxy. Check Use proxy for: with only HTTP selected, https:// requests skip the proxy.

The proxy error codes guide decodes 403, 429 and 502 once the proxy connects. For the same check from a terminal, see the curl proxy guide; to call APIs through a proxy on a schedule, see n8n.