Tutorials 4 min read

Postman Proxy Setup: Send API Requests Through a Proxy (2026)

Postman can route requests through an authenticated proxy in a few clicks. Here is where the settings live and how to test geo-specific API responses.

A Postman proxy setup is useful when you need to see how an API responds from another country, when you're testing rate limits from different IPs, or when your company network only allows outbound traffic through a proxy. The desktop app supports custom authenticated proxies directly. This guide shows where the settings are, what each field means and how to check the proxy is actually being used.

Before You Start: Desktop App vs Web

Proxy settings apply to the Postman desktop app, and to the web version only when requests go through the desktop agent. Requests sent from the browser via the cloud agent don't use your proxy settings at all. If you're on the web version and the proxy seems ignored, switch to the desktop app first.

Step-by-Step Postman Proxy Settings

  1. Open Settings (the gear icon in the header, then Settings).
  2. Go to the Proxy tab.
  3. Turn off "Use the system proxy" if it's on, so it doesn't conflict.
  4. Turn on "Use custom proxy configuration".
  5. Tick both HTTP and HTTPS under Proxy Type.
  6. Enter global.nodeproxies.xyz as the Proxy Server and 8080 as the port.
  7. Turn on Proxy Auth and enter your proxy username and password.
  8. Add anything that shouldn't go through the proxy to Proxy Bypass, such as localhost,127.0.0.1.

Settings save immediately. There's no per-request proxy option; the configuration applies to every request the app sends until you switch it off.

Verify the Proxy Is Being Used

Create a GET request to https://api.ipify.org?format=json and send it. The response body shows the IP the server saw. Turn the custom proxy off, send again, and compare. If both show the same IP, the proxy isn't in use. Check the Postman Console (View, then Show Postman Console) for errors such as a 407 from the proxy.

Testing Geo-Dependent APIs by Country

Many APIs change currency, language, content availability or pricing based on the caller's IP. To compare, change only the username in Proxy Auth:

  • USERNAME-country-us for a United States IP
  • USERNAME-country-gb for a United Kingdom IP
  • USERNAME-country-de for a German IP

Send the same request after each change and save the responses as examples on the request. That gives you a side-by-side record of what each market sees, which is handy for QA and for documenting regional behaviour to your team. Available countries are listed on the residential proxies page.

Sticky vs Rotating IPs in Postman

With a plain username, every request leaves from a new IP. That's good for checking how an API treats first-time callers, but bad for flows like "log in, then call an endpoint with the token" when the API binds tokens to IPs. For those, add a session to the username, for example USERNAME-country-us-session-qa1-time-30. Every request keeps the same IP for 30 minutes. Change qa1 to qa2 to get a new one.

Testing Rate Limits Responsibly

Rotating IPs make it easy to see whether an API limits per IP, per key or both. Do this only against APIs you own or have permission to test, and keep volumes small. If you hit 429 responses from a third-party API you're allowed to use, the right fix is backing off, not rotating harder. The reasoning is covered in why proxies get blocked.

Running the Same Requests in Newman or Code

Postman's proxy settings don't travel with an exported collection. When you run a collection with the Newman CLI, set the proxy through environment variables instead:

export HTTPS_PROXY='http://USERNAME-country-us:[email protected]:8080'
export HTTP_PROXY="$HTTPS_PROXY"
newman run my-collection.json

Newman respects these variables. If you later port the requests to a script, the curl proxy guide and the Node.js proxy guide show the equivalent code.

Troubleshooting Postman Proxy Errors

  • "Could not send request" with tunneling socket errors: wrong host or port, or a firewall blocking 8080.
  • 407 Proxy Authentication Required: Proxy Auth is off, or the username/password is wrong, or the plan isn't active.
  • 402 from the proxy: your plan is out of bandwidth.
  • SSL errors only through the proxy: turn off "SSL certificate verification" only for testing your own self-signed servers, never as a general fix.
  • Proxy ignored: you're using the browser with the cloud agent, or "Use the system proxy" is overriding your settings.

Setting Up Postman with NodeProxies

Use global.nodeproxies.xyz on port 8080 with your dashboard credentials. API testing uses very little bandwidth, so the smallest plans go a long way; you can buy from 100 MB. Datacenter proxies are the cheapest option for testing your own APIs, and residential IPs are better when you need to see what real users in a country see. See pricing or register with a $3 minimum deposit.

FAQ

Where are proxy settings in Postman?

Open Settings from the gear icon and choose the Proxy tab. Turn on "Use custom proxy configuration" to enter your own server and credentials.

Can I use a different proxy for each request in Postman?

Not natively. The proxy is global to the app, so change the username between requests or use Newman with environment variables per run.

Does Postman support SOCKS5 proxies?

The custom proxy settings are built for HTTP and HTTPS proxies. Use the HTTP endpoint on port 8080; it tunnels HTTPS requests securely.

Why does Postman show my real IP even with a proxy set?

Most often the request was sent via the cloud agent in the web app, or the bypass list matches the host. Use the desktop app and check the bypass list.

NodeProxies

Ready to get started?

90M+ residential, mobile & datacenter proxies. Datacenter from $0.30/GB, residential from $0.42/GB. No contracts.

Create free account