# Postman Proxy Settings: Setup, Bypass, Fixes

> Postman proxy settings step by step: custom proxy, http on port 8080, Proxy auth, the bypass list, a check of the exit country and a fix for statusCode=407.

[Home](https://quanticdata.io/) / [Blog](https://quanticdata.io/blog/) / Postman Proxy Settings: Setup, Bypass, Fixes

# Postman proxy settings: add a proxy, choose which requests use it, fix the 407

Proxies · Oct 23, 2026 · 12 min read · By [Aldo Morese](https://quanticdata.io/about/), founder of QuanticData

![Setting up a proxy in Postman in four steps: generate a sticky India line in the QuanticData endpoint generator, open Settings > Proxy and turn on Use custom proxy configuration with http, the host and port 8080, turn on Proxy auth with the whole username and the password, then send GET https://ipinfo.io/json to see the exit; the card lists the three things to verify when Postman answers statusCode=407.](https://quanticdata.io/blog/postman-proxy-setup/hero.webp?v=20261023h)

On this page

- [What you need before you start](https://quanticdata.io/blog/postman-proxy-setup/#what-you-need-before-you-start)
- [Postman's three proxy options, and the one to use](https://quanticdata.io/blog/postman-proxy-setup/#postman-s-three-proxy-options-and-the-one-to-use)
- [Step by step: Residential Premium in Postman](https://quanticdata.io/blog/postman-proxy-setup/#step-by-step-residential-premium-in-postman)
- [Check where your requests come from](https://quanticdata.io/blog/postman-proxy-setup/#check-where-your-requests-come-from)
- [Which requests go through the proxy](https://quanticdata.io/blog/postman-proxy-setup/#which-requests-go-through-the-proxy)
- [One session or a new IP for each request](https://quanticdata.io/blog/postman-proxy-setup/#one-session-or-a-new-ip-for-each-request)
- [ISP proxies in Postman](https://quanticdata.io/blog/postman-proxy-setup/#isp-proxies-in-postman)
- [Mobile proxies in Postman](https://quanticdata.io/blog/postman-proxy-setup/#mobile-proxies-in-postman)
- [Which proxy for which test](https://quanticdata.io/blog/postman-proxy-setup/#which-proxy-for-which-test)
- [HTTP or SOCKS5 in Postman](https://quanticdata.io/blog/postman-proxy-setup/#http-or-socks5-in-postman)
- [Postman proxy not working: errors and fixes](https://quanticdata.io/blog/postman-proxy-setup/#postman-proxy-not-working-errors-and-fixes)
- [Not the same thing: Postman's built-in proxy](https://quanticdata.io/blog/postman-proxy-setup/#not-the-same-thing-postman-s-built-in-proxy)
- [Before you test](https://quanticdata.io/blog/postman-proxy-setup/#before-you-test)

To use a proxy in Postman, open Settings > Proxy, turn on Use custom proxy configuration, choose http, enter the host and port 8080, turn on Proxy auth with the whole username and the password, then send GET https://ipinfo.io/json to see where your requests come from. Hosts listed in Proxy bypass skip the proxy.

Postman sends API requests from your own connection unless you tell it otherwise. With a proxy, the API you test sees the proxy's IP address and its country: that is how you check geo rules, local content and per-IP rate limits from your desk. What trips people up is which requests actually use the proxy, the login, and error messages that never say "proxy". The field names below are the ones in Postman's documentation for the current desktop app (version 12); the values come from the QuanticData endpoint generator.

## What you need before you start

- **The Postman desktop app.** The steps below are for the desktop app on Windows, macOS or Linux.
- **A proxy plan:** Residential Premium, ISP or mobile. All of them go in the same box; the table further down says which one fits which test.
- **Four values:** host, port, username and password. In the QuanticData dashboard they are under My proxies, on the plan's page, in the Endpoint generator: Connection details shows them one by one, which is how Postman asks for them.

**Try it on your own targets.** Every QuanticData account gets $2 of free API usage per month.

[Start free — $2/month included](https://quanticdata.io/signup/?utm_source=blog&utm_medium=website&utm_campaign=blog-inline&utm_content=postman-proxy-setup) · [Explore Residential Proxies from $0.80/GB](https://quanticdata.io/residential-proxies/)

## Postman's three proxy options, and the one to use

The Proxy tab of Postman's settings has three switches under Proxy configurations for sending requests:

- **Use system proxy** sends requests through the proxy configured in your operating system, with an extra switch to respect the HTTP_PROXY, HTTPS_PROXY and NO_PROXY environment variables.
- **Use custom proxy configuration** sends requests through a proxy you type into Postman itself. This is the one to use: it changes only Postman, not every program on the computer, and it has its own login fields.
- **Default proxy configuration**, higher on the same tab, only adds a username and password for a system proxy and restarts Postman. It is not needed for a custom proxy.

If both the system proxy and the custom proxy are on, Postman uses the custom proxy. Turning the system proxy off anyway keeps the setup easy to read.

## Step by step: Residential Premium in Postman

![The QuanticData Endpoint generator for a Residential Premium plan: India selected as the country, Session set to Sticky with a 30-minute TTL, HTTP protocol, output format host:port:user:pass and the preview line, with the username and password blurred](https://quanticdata.io/blog/postman-proxy-setup/quanticdata-generator-india-sticky.webp)

*Step 1 in the QuanticData dashboard: the country your requests should come from, a sticky session and the HTTP protocol.*

1. **Generate the line.** In the QuanticData dashboard open My proxies, then your plan. In the Endpoint generator choose the Country (India in this example, with a Region or City if you need one), set Session to Sticky with a Session TTL (minutes) longer than your test, and keep Protocol on HTTP.
2. **Open Connection details.** It lists Host, Port, Username and Password with a copy button each. Postman wants them in separate fields.
3. **Open the proxy settings.** In Postman click the Settings icon in the header, then Settings, then the Proxy tab.
4. **Turn on Use custom proxy configuration.** Turn off Use system proxy and the environment variables switch.
5. **Use proxy for: HTTP and HTTPS.** Both are ticked by default. Leave them that way so every request goes through the proxy.
6. **Proxy server.** Choose `http` in the list, type `residentialpremium.quantumproxies.io` after the :// (without http:// in front) and `8080` as the port.
7. **Turn on Proxy auth.** Paste the username whole, for example `USER-country-in-sid-pm01-ttl-60m`, then the password.
8. **Close Settings and send a request.** The proxy applies to the next request you send from the Builder.

![Connection details in the QuanticData Endpoint generator: Host residentialpremium.quantumproxies.io, Port 8080, the username with the India targeting and the session, and the password, each with a copy button, credentials blurred](https://quanticdata.io/blog/postman-proxy-setup/quanticdata-generator-connection-details.webp)

*Step 2: the same proxy as four values, the way Postman asks for them.*

![The Postman box Proxy configurations for sending requests with five numbered markers: 1 the Proxy tab of Settings, 2 Use custom proxy configuration on, 3 HTTP and HTTPS ticked under Use proxy for, 4 Proxy server http :// residentialpremium.quantumproxies.io : 8080, 5 Proxy auth on with the username USER-country-in-sid-pm01-ttl-60m and the password; a real check of an India line gives Ludhiana, Punjab, Asia/Kolkata](https://quanticdata.io/blog/postman-proxy-setup/postman-custom-proxy-residential-premium.webp)

*Steps 3 to 7 in Postman, redrawn with our values. The host field shows only its first characters, as in the app.*

The username carries the targeting: `-country-in` picks the exit country, `-sid-pm01` names the session and `-ttl-60m` keeps the same IP for 60 minutes. Copy it whole. A username cut at the first dash still logs in, but your requests then leave from a random country.

## Check where your requests come from

Postman has no proxy test button, so send a request that answers with your IP and its location:

1. Open a new request, keep the method on GET and enter `https://ipinfo.io/json`.
2. Click Send.
3. A 200 OK means the proxy accepted the login. The body shows the IP the API saw, with its city, region, country and time zone.

![The Postman request builder with GET https://ipinfo.io/json sent through the QuanticData proxy: 200 OK and the JSON answer with the IP masked as 203.76.x.x, city Ludhiana, region Punjab, country IN and timezone Asia/Kolkata, with four numbered steps](https://quanticdata.io/blog/postman-proxy-setup/postman-ipinfo-check-india.webp)

*The check in Postman: the body is the real answer for a QuanticData India line on 23 October 2026, IP masked. Redrawn screen.*

Our own run of this check with an India sticky line on 23 October 2026 answered from Ludhiana, region Punjab, country IN, time zone Asia/Kolkata, on an Indian home broadband network (AS133661). That is the location every API you call from Postman sees until the session ends. If the answer shows your own IP instead, the request did not go through the proxy: the next section says why.

## Which requests go through the proxy

The custom proxy is set for the whole app, not per request; there is no proxy field in a request's own Settings tab. Four rules decide what goes through it:

1. **Use custom proxy configuration is on.** It wins over Use system proxy when both are on.
2. **Use proxy for** picks the schemes. With HTTP and HTTPS both ticked, every request goes through the proxy; untick HTTP and requests to `http://` URLs go direct.
3. **Proxy bypass** lists hosts that always go direct, separated by commas. A star covers subdomains, as in Postman's own example `*.example.com`. Put your local and internal APIs here, for example `localhost, 127.0.0.1, *.corp.example.com`, so they keep working while the proxy is on.
4. **Only requests sent through the Builder** use it. The box says so itself: "These configurations do not apply to any Postman services".

![The Postman custom proxy box with Proxy bypass set to localhost, 127.0.0.1, *.corp.example.com and four numbered markers: the custom proxy switch, the HTTP and HTTPS boxes under Use proxy for, the Proxy bypass list and the line saying the settings do not apply to Postman services; a note explains how to test the bypass with ipinfo.io](https://quanticdata.io/blog/postman-proxy-setup/postman-proxy-bypass.webp)

*Which requests use the proxy and which go direct. Redrawn screen with our values.*

To see the rules at work, add `ipinfo.io` to Proxy bypass and send the check again: your own IP comes back. Remove it and the proxy's IP returns. To test one request without the proxy, the bypass list is the quickest way; to stop using the proxy altogether, turn off Use custom proxy configuration.

Two more things change with a proxy on. Postman sends the requests over HTTP/1.x, whatever HTTP version is set in its settings. And the Console, opened from the Postman footer, logs the proxy configuration used for every request, which is the first place to look when a request does not go where you expect.

## One session or a new IP for each request

The username decides how the IP behaves across your requests:

| Username | What the API sees | Use it for |
| --- | --- | --- |
| `USER-country-in-sid-pm01-ttl-60m` | One IP in India for up to 60 minutes; up to 1440 minutes with `-ttl-1440m` | Logins, sessions, collections whose requests depend on each other |
| `USER-country-in` | A new IP in India for each request | Checking what different visitors in one country get, rate limits per IP |
| `USER-country-de-sid-pm02-ttl-60m` | One IP in Germany | The same API as German users see it: change the username, send again |

Postman holds one custom proxy at a time, so switching country means editing the username in Settings > Proxy. For a new IP on Residential Premium or mobile, change the session ID, `-sid-pm02` instead of `-sid-pm01`.

## ISP proxies in Postman

An ISP proxy is one fixed IP address that stays the same for months. In Postman it is the answer when an API, a partner's sandbox or a staging server only accepts calls from addresses on its allowlist: give them the ISP IP and send your requests through it.

![The Assigned IPs panel of a QuanticData ISP plan: Protocol HTTP / HTTPS, output format IP:Port:Username:Password, five IPs masked with port 50100 and username USER, and the formatted output ready to copy](https://quanticdata.io/blog/postman-proxy-setup/quanticdata-isp-assigned-ips.webp)

*Proxy endpoints, Assigned IPs: every line is one fixed IP with its port and login. Sample IPs masked.*

1. **Copy one line** from Assigned IPs, with Protocol on HTTP / HTTPS and the format IP:Port:Username:Password.
2. **Proxy server:** `http`, the IP after the ://, and the port of that line, 50100 in the example.
3. **Proxy auth:** the Username and Password of the same line.
4. **Send the check.** ipinfo.io answers with that same IP every time.

![The Postman custom proxy box with a QuanticData ISP proxy: Proxy server http :// 82.x.x.127 (masked) : 50100, Proxy auth on with Username USER and the password, with three numbered steps and a note that the check shows the same IP every time](https://quanticdata.io/blog/postman-proxy-setup/postman-custom-proxy-isp.webp)

*An ISP line in the same box: every request leaves from this one IP. Redrawn screen with our values.*

## Mobile proxies in Postman

Mobile lines go in the same fields. The host is `mobile.quantumproxies.io` on the Global gateway (USA, EU and Asia gateways are in the generator too), the port is 8080, and the username carries `-type-mobile`, for example `USER-country-in-type-mobile-sid-pm02-ttl-60m`. Use them to test an API the way an app on a phone on a carrier network reaches it.

![The QuanticData Endpoint generator for a Mobile plan: India selected, Global, USA, EU and Asia gateways, Sticky session, HTTP 8080 or SOCKS5 1080, output format host:port:user:pass and the preview line with -type-mobile, credentials blurred, and the IP whitelist section below](https://quanticdata.io/blog/postman-proxy-setup/quanticdata-generator-mobile-india.webp)

*Mobile: gateway, protocol and port, and the IP whitelist section.*

Mobile plans also offer IP whitelist authentication: add your own IP in the generator, take the host and port it gives you, and leave Proxy auth off. Residential Premium and ISP lines always log in with username and password.

## Which proxy for which test

| Proxy type | In Postman's Proxy server | Good for |
| --- | --- | --- |
| Residential Premium | http :// residentialpremium.quantumproxies.io : 8080, the whole username with country, region, city or ISP | An API as users in a given country reach it: geo rules, local prices and content |
| ISP | http :// the IP of one Assigned IPs line : 50100, its username and password | One fixed address to put on an API allowlist |
| Mobile | http :// mobile.quantumproxies.io : 8080, -type-mobile in the username, or IP whitelist without Proxy auth | APIs that answer phones on carrier networks differently |

The plans are on the pages for [QuanticData residential proxies](https://quanticdata.io/residential-proxies/), [ISP proxies](https://quanticdata.io/isp-proxies/), [mobile proxies](https://quanticdata.io/mobile-proxies/) and [India residential proxies](https://quanticdata.io/proxies/india/).

## HTTP or SOCKS5 in Postman

Postman's Proxy server list offers HTTP, SOCKS5, SOCKS5H, SOCKS4 and SOCKS4A, and Postman only sends HTTP and HTTPS requests through a SOCKS proxy. Its documentation describes Proxy auth as basic authentication, the login scheme of HTTP proxies, so this guide uses `http` with the HTTP port: 8080 on Residential Premium and mobile, 50100 on ISP. HTTPS requests still travel encrypted end to end: Postman opens a tunnel through the proxy to the API, which is what "tunneling socket" in its error messages refers to. If you need SOCKS5 for another reason, QuanticData's SOCKS5 ports are 1080 on Residential Premium and mobile and 50101 on ISP (see [SOCKS5 proxies](https://quanticdata.io/socks5-proxies/)). What breaks a setup is a type that does not match its port.

## Postman proxy not working: errors and fixes

When a request fails, the response area shows the error and the Console in the Postman footer shows it again with the request. The most common one with a proxy is `Error: tunneling socket could not be established, statusCode=407`: the proxy answered 407 Proxy Authentication Required to the tunnel Postman opens for an https:// URL. On QuanticData that means no login was sent or a wrong one: Proxy auth is off, the username is cut, or the password is not the one in the dashboard.

![The Postman Console with the request GET https://ipinfo.io/json and the red line Error: tunneling socket could not be established, statusCode=407; below, what to check in order: Proxy auth on, the whole username, the password from the dashboard, a plan that is active with traffic left](https://quanticdata.io/blog/postman-proxy-setup/postman-console-statuscode-407.webp)

*The 407 error as the Console logs it, and the order of the checks. Redrawn screen.*

| What you see | Usual cause | Fix |
| --- | --- | --- |
| tunneling socket could not be established, statusCode=407 | Proxy auth off, a cut username or a wrong password: the gateway answers 407 | Turn on Proxy auth, paste the whole username and the password again from Connection details |
| 407 Proxy Authentication Required as the response status | The same refused login, on a request to an `http://` URL | The same fix; see also [how to fix 407 Proxy Authentication Required](https://quanticdata.io/blog/how-to-fix-407-proxy-authentication-required/) |
| tunneling socket could not be established, cause=getaddrinfo ENOTFOUND | The proxy host cannot be found: a typo, or a protocol typed in front of it | Copy the host again, alone, as Postman's docs ask: `residentialpremium.quantumproxies.io` |
| An error ending in ECONNRESET or socket hang up | The type does not match the port: http on 1080, the SOCKS5 port, is reset at once | http with 8080 (ISP: the port of the line), or socks5 with 1080 |
| Requests still come from your own IP | The host is in Proxy bypass, the scheme is unticked in Use proxy for, or proxy environment variables are set | Check both fields; remove HTTP_PROXY and HTTPS_PROXY from your system, or start Postman without them |
| 502 Bad Gateway | The proxy reached out, but the API's server did not answer properly | Check the URL, send again; with a sticky line try a new session ID |
| Worked yesterday, fails today | The plan expired or its traffic is used up | Check status, remaining traffic and expiry in My proxies |

One test outside Postman settles most cases in a minute. If this returns an address in the right country, the proxy works and the problem is in Postman's fields; more on this in [how to use a proxy with curl](https://quanticdata.io/blog/how-to-use-a-proxy-with-curl/):

```bash
curl -x http://residentialpremium.quantumproxies.io:8080 \
  -U "USER-country-in-sid-pm01-ttl-60m:PASS" https://ipinfo.io/json
```

The same values work in code once a collection moves out of Postman, for example in [Python Requests](https://quanticdata.io/blog/how-to-use-a-proxy-with-python-requests/).

## Not the same thing: Postman's built-in proxy

Postman also has a built-in proxy for capturing traffic, the subject of its pages on capturing API requests and of the searches for a "Postman proxy certificate". It works the other way round: other apps or a phone send their traffic through Postman so it can record the requests. It has nothing to do with sending your requests out through a proxy server, and you do not need its certificate for anything in this guide.

## Before you test

A proxy changes where your requests come from, not what an API allows. Test APIs you own or are allowed to call, keep to their terms and rate limits, and use test accounts for anything that logs in.

### Sources & further reading

- [Postman documentation: Configure Postman to use a proxy server](https://learning.postman.com/docs/getting-started/installation/proxy)
- [Postman documentation: Debug API requests in Postman](https://learning.postman.com/docs/use/send-requests/response-data/troubleshooting-api-requests)
- [Newman README: Configuring Proxy](https://github.com/postmanlabs/newman#configuring-proxy)
- [Postman Community: Tunneling socket could not be established, statusCode=407](https://community.postman.com/t/tunneling-socket-could-not-be-established-statuscode-407/58551)
- [RFC 9110 HTTP Semantics: 407 Proxy Authentication Required](https://www.rfc-editor.org/rfc/rfc9110#name-407-proxy-authentication-re)

## FAQ

Quick answers on postman proxy settings.

[Something else? Ask us](mailto:hello@quanticdata.io)

### Where are the proxy settings in Postman?

In the desktop app click the Settings icon in the header, then Settings, then the Proxy tab. Under Proxy configurations for sending requests turn on Use custom proxy configuration, then fill in Proxy server, Proxy auth and, if you need it, Proxy bypass.

### How do I use a proxy with a username and password in Postman?

Turn on Proxy auth in the custom proxy configuration and enter the Username and Password there. With QuanticData paste the whole username, including the targeting after the first dash, for example USER-country-in-sid-pm01-ttl-60m, and choose http with port 8080 as the Proxy server.

### Can I set a proxy for a single request in Postman?

No: the custom proxy is set for the whole app and a request's own Settings tab has no proxy option. To send some requests direct, list their hosts in Proxy bypass, separated by commas; to stop using the proxy, turn off Use custom proxy configuration.

### Does Postman support SOCKS5 proxies?

Yes. The Proxy server list offers HTTP, SOCKS5, SOCKS5H, SOCKS4 and SOCKS4A, and Postman sends only HTTP and HTTPS requests through a SOCKS proxy. Its Proxy auth is basic authentication, so with a QuanticData login this guide uses http on port 8080; the SOCKS5 ports are 1080 on Residential Premium and mobile and 50101 on ISP.

### Why does Postman say "tunneling socket could not be established, statusCode=407"?

The proxy refused the login with 407 Proxy Authentication Required. Turn on Proxy auth, paste the whole username and the password again, and check in My proxies that the plan is active with traffic left. If the same values work with curl, the problem is in Postman's fields.

### Why do my Postman requests still use my own IP?

The request skipped the proxy: its host is in Proxy bypass, its scheme is unticked under Use proxy for, Use custom proxy configuration is off, or HTTP_PROXY and HTTPS_PROXY environment variables are set, which make Postman use the system proxy. Fix the field, or start Postman without those variables, and send GET https://ipinfo.io/json again.

### Does Newman use the proxy set in the Postman app?

Newman, Postman's command-line collection runner, is configured separately: according to its README it takes the proxy from the HTTP_PROXY, HTTPS_PROXY and NO_PROXY environment variables of the shell it runs in, not from the app's Settings.

## Test every API from the country your users are in

Residential Premium, ISP and mobile proxies with country targeting and sticky sessions up to 1440 minutes, copied from the endpoint generator into Postman's Proxy settings.

[Start free — $2/month included](https://quanticdata.io/signup/?utm_source=blog&utm_medium=website&utm_campaign=blog-end&utm_content=postman-proxy-setup) · [Explore Residential Proxies from $0.80/GB](https://quanticdata.io/residential-proxies/)

## Related reading

- [Brave Browser Proxy: Set Up a Proxy in Brave](https://quanticdata.io/blog/brave-proxy-setup/): Proxies · Brave sends you to the computer's proxy settings, which change every app. Quantum Proxies Manager, a free extension from the Chrome Web Store, sets the proxy for Brave alone and answers its sign-in. Below: the install prompt, private and Tor windows, Shields, the WebRTC setting, ISP and mobile plans, the check and the fixes.
- [How to Use SocksDroid on Android: SOCKS5 Setup](https://quanticdata.io/blog/socksdroid-proxy-setup/): Proxies · Add a profile, put the host in Server IP and the SOCKS5 port in Server Port, tick Username & Password Authentication, fill in Username and Password, turn on the switch and allow the VPN request. Below: every field of the app, a real check from Istanbul, only some apps on the proxy, Residential Premium, ISP and Mobile lines, and what to check when nothing loads.
- [WebHarvy Proxy: Settings, Rotation and Fixes](https://quanticdata.io/blog/webharvy-proxy-setup/): Proxies · Open Home, Settings, Proxy Settings, tick Enable network connection via Proxy Server, pick Type HTTP, enter the address and port, tick Requires Authentication, click + and Apply. Below: Residential Premium, ISP and mobile values, a check in WebHarvy's own browser, Rotate proxies with an imported list, editing a proxy and a fix for Error Code -375.

---

Source: https://quanticdata.io/blog/postman-proxy-setup/ · Site index for AI: https://quanticdata.io/llms.txt