Sending Postman Requests Through a Proxy, With Login and Exceptions
By the ProxyV4 Engineering Team · Updated:
Postman proxy settings live in the desktop app under Settings, on the Proxy tab: switch on Use custom proxy configuration, enter the proxy host and port, turn on Proxy auth for a username and password, and list any hosts that should go direct under Proxy bypass. The details that trip people up are elsewhere: environment variables that silently override the app, the difference between the app's own traffic and your requests, and how the web app's agents change where a request comes from.
Two kinds of proxy setting in Postman
Open Settings from the gear icon in the header (some versions label the next screen App settings) and choose the Proxy tab. The page is split into two groups that are easy to confuse.
Default proxy configuration covers the desktop app's own traffic: signing in, syncing workspaces, loading collections. It is inherited from your operating system, and its only control is an option to add credentials if that proxy requires authentication. It exists only in the desktop app, and changing it asks you to restart Postman.
Proxy configurations for sending requests is the part that affects your API calls. This is where you pick between the system proxy and a custom proxy, and it is the subject of the rest of this guide. Labels shift a little between versions, but these two groups have been stable for several releases.
System proxy or custom proxy
Both options can be on at once. When they are, the custom configuration wins, so turn the system proxy off when you want to be sure which path a request takes.
Use system proxy
Requests follow the operating system's proxy, the same one your browser uses. A sub-option, Respect HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables, makes Postman read those variables instead. This is convenient on a corporate network where IT already set things up, and inconvenient when you want only Postman behind a particular proxy, because the whole machine is then affected.
Use custom proxy configuration
A proxy just for Postman requests, independent of the OS. You choose whether it applies to HTTP, HTTPS or both (both by default), pick the proxy protocol from a dropdown, and enter the server. Recent versions list HTTP, SOCKS5, SOCKS5H, SOCKS4 and SOCKS4A; with SOCKS5H the proxy resolves hostnames, which keeps DNS lookups off your local network. Whatever the proxy protocol, Postman only sends HTTP and HTTPS requests through it.
The environment-variable trap
If HTTP_PROXY, HTTPS_PROXY or their lowercase forms are set in the environment Postman starts from, Postman uses the system proxy and ignores what you entered on the Proxy tab. This is the usual reason a carefully filled-in custom proxy appears to do nothing. Remove the variables, or start Postman from a small script that clears them first.
# Linux: start Postman with proxy variables cleared (adjust the path to your install)
env -u HTTP_PROXY -u HTTPS_PROXY -u http_proxy -u https_proxy /opt/Postman/Postman &The bypass list and what belongs on it
Proxy bypass takes a comma-separated list of hosts that skip the custom proxy. Use it for anything that should not leave your network through a third party, and for services that reject foreign addresses.
localhost, 127.0.0.1, api.internal.example, auth.example.comGood candidates are local mock servers, staging APIs on a private network, and an identity provider that flags logins from unexpected countries. Add the token endpoint here if you test geo-dependent APIs but authenticate against a service that should always see your usual address. Requests to hosts on the list go direct, which is easy to forget when a test result looks wrong, so keep the list short.
Proving a request really used the proxy
When you test an API through a proxy, Postman shows no proxy indicator next to the response, so check from the response itself. Create a request to an IP echo service and attach a test that compares the address with the proxy you expect.
// Tests tab of GET https://api.ipify.org?format=json
const expected = pm.environment.get('expected_exit_ip');
pm.test('Exit IP matches the proxy', () => {
pm.expect(pm.response.json().ip).to.eql(expected);
});Store expected_exit_ip in an environment and run this request first in a collection run, so a misconfigured proxy fails fast instead of producing misleading results further down. The Postman Console (View menu, or the console icon in the footer) shows the full request and any network error, which is where tunnel and authentication failures appear. To confirm the proxy line itself before involving Postman, use the proxy checker.
The web app, the agents and Newman
Which settings apply depends on where the request is actually sent from, and that is not always your computer.
Web app with the Desktop Agent
In Postman on the web, requests are sent by an agent you choose in the footer. The Desktop Agent runs on your machine and sends requests from there, so your local network path applies, but the web app cannot set the default proxy, and the available proxy controls depend on the agent and version. For dependable proxy testing, use the desktop app.
Cloud and browser agents
With the Cloud Agent, requests leave from Postman's own infrastructure, so neither your machine's proxy settings nor private hosts on your network are in the path. The Browser Agent is limited by the browser's own security rules. If an exit IP matters to your test, these agents will not give you the result you expect.
Newman and the Postman CLI
Command-line runners do not read the desktop app's Proxy tab. In CI, set the standard HTTPS_PROXY and NO_PROXY variables for the job and check your runner's documentation for any proxy flags of its own.
Testing geo-dependent APIs from several countries
A common reason to proxy Postman is checking how an API responds by region: localized pricing, currency, content availability, tax rules, or a geo-fence that should block some countries. That calls for a stable, known address in each country, not a random pool, because a test that passes on Monday should hit the same IP on Tuesday. ProxyV4 private IPv4 is available in the United States, Vietnam, Japan, South Korea, Singapore, the United Kingdom and Hong Kong, and static ISP addresses in the US and Vietnam are useful when an API treats datacenter ranges differently.
Each proxy supports HTTP and SOCKS5 with a username and password, which maps onto Postman's custom proxy fields, keeps one tenant for the whole term, and keeps its address when renewed. Because Postman's proxy is an app-wide setting rather than per environment, keep a note of which country each line belongs to and switch the server field when you change region. Confirm the location of each line with the free proxy checker before you trust a test result.
This setup does not fit if your API only responds to mobile carrier networks, or if you need a new IP on every request; ProxyV4 sells neither. If one country is enough, a single IP is fine to start with; the price list shows per-IP rates and term options.
Common errors behind a proxy
- 407 or "tunneling socket could not be established, statusCode=407": Proxy auth is off, or the username or password is wrong. See the 407 guide.
- Proxy settings ignored: proxy environment variables are set, the host is on the bypass list, or the request runs on the Cloud Agent.
- ECONNREFUSED or ETIMEDOUT to the proxy address: wrong port, or the proxy mode was switched and the port changed; copy the line again from your dashboard.
- SSL errors only behind the proxy: a corporate inspection proxy is re-signing traffic. Add its CA certificate under the Certificates tab rather than turning off SSL verification globally.
- Host field rejected: enter only the hostname or IP, without
http://; the protocol comes from the dropdown.
Step by step
- 1
Open the Proxy tab
In the Postman desktop app, open Settings from the gear icon and select the Proxy tab.
- 2
Switch to a custom proxy
Turn off Use system proxy and turn on Use custom proxy configuration, leaving both HTTP and HTTPS selected.
- 3
Enter the server
Choose HTTP as the protocol, type the IP in the host field and the port beside it, taken from your
ip:port:user:passline. - 4
Add the login
Turn on Proxy auth and enter the username and password from the same line.
- 5
Set exceptions and test
Add local or internal hosts to Proxy bypass, then send a request to an IP echo endpoint and confirm the proxy address comes back.
Frequently asked questions
Does Postman support SOCKS5 proxies?
Recent desktop versions offer SOCKS5 and SOCKS5H in the custom proxy protocol dropdown, with the same Proxy auth fields. Older versions only accepted HTTP proxies, so update if you do not see the option.
Can I set a different proxy per collection or environment?
No. The custom proxy is an app-wide setting. Switch it when you change region, or run collections through a command-line runner with different proxy variables per job.
Why does Postman ignore my custom proxy?
Most often because HTTP_PROXY or HTTPS_PROXY is set in the environment, which makes Postman use the system proxy. The host may also be on your bypass list.
Where should I keep the proxy password in a team workspace?
Enter it on the Proxy tab of each person's app rather than in shared environments, collection variables or request scripts, where every workspace member can read it.
Do I need a separate proxy for HTTP and SOCKS5?
Not with ProxyV4. Each order can serve HTTP only, SOCKS5 only, or both on the same port, chosen from the order's page in your dashboard.
Test geo-dependent APIs from seven countries
Get a fixed private IPv4 in the US, Vietnam, Japan, South Korea, Singapore, the UK or Hong Kong, with HTTP and SOCKS5 login for Postman.
Get a static IP