Configure Postman custom proxy settings with separate host and authentication fields, enable HTTPS proxying, then verify one authorized request.
Postman Desktop can send requests through a custom residential proxy. Menu names can move between versions, but the safe mapping stays the same: enable the custom proxy, use the host without protocol or credentials, set port separately, enable proxying for HTTPS requests, and enter proxy auth in its own fields. All values here are fake. Not for mainland China.
Values to prepare
| Field | Fake example | Rule |
|---|---|---|
| Proxy host | `proxy.example.invalid` | No protocol, path, or credentials |
| Proxy port | `10000` | Use the console value |
| Proxy username / password | `USER_EXAMPLE` / `PASS_EXAMPLE_NOT_REAL` | Use separate Proxy Auth fields |
Configure Postman
- Open the desktop app's Settings and find Proxy. The exact menu label can vary by version.
- Turn on Custom proxy configuration (or the equivalent switch).
- Enter `proxy.example.invalid` as host and `10000` as port. Do not add a protocol or credentials to the host.
- Enable the option that applies the proxy to HTTPS requests.
- Enable proxy authentication and enter `USER_EXAMPLE` and `PASS_EXAMPLE_NOT_REAL` in their separate fields.
- Save or close Settings, then send one request to an authorized URL.
| Switch | Recommended first check | Why |
|---|---|---|
| Use system proxy | Off when testing the custom gateway | Avoid two proxy layers while diagnosing |
| Custom proxy | On | Sends the request through the specified gateway |
| Proxy HTTPS requests | On | Allows HTTPS destinations through the gateway |
| Proxy Auth | On for username/password orders | Supplies gateway authentication |
ZTProxy does not claim that IP allowlist authentication is an official Postman capability. Use the username/password authentication returned by the console unless your actual environment and Postman version explicitly support another method.
Verify the result
| Result | Meaning | Action |
|---|---|---|
| Expected response | Proxy path worked | Confirm the source IP on an approved endpoint |
| HTTP 407 | Authentication missing or rejected | Re-copy auth and ensure it is in Proxy Auth, not request Authorization |
| Timeout | Gateway, protocol, firewall, DNS, or target issue | Compare with curl testing |
| Direct local IP | Proxy switch not applied or bypassed | Recheck custom proxy and system-proxy settings |
Use rotating residential for changing exits or static residential for a term-long fixed exit. Details: proxy format, HTTP / SOCKS5 setup, Docs quickstart, and 407 / timeout troubleshooting.
FAQ
What does HTTP 407 mean?
The gateway reached your client but rejected or did not receive proxy authentication. Re-copy the username and password from the console and keep them in the authentication fields.
Why does the request time out?
Check protocol, host, port, local firewall, DNS, and the authorized target. Then reduce the test to one request with a finite timeout.
Should the host include the protocol?
No. Keep the host as a hostname. Add the scheme only where the library expects a proxy URL.
Should I enable HTTPS proxying?
Yes when sending HTTPS requests through the HTTP proxy gateway. Postman labels can vary by desktop version, so confirm the current Settings screen.
How do I confirm the exit?
Request an authorized page that reports the source IP, compare it with your intended region or static order, and do not treat a gateway hostname as the exit.
Can a sticky session replace a static IP?
No. Sticky keeps a rotating exit for a limited window when available; a static residential order keeps its assigned exit for the order term.
May I use these placeholder credentials?
No. The example domain cannot resolve and every credential shown here is fake. Copy current values from the console.
Can I use this in mainland China?
No. ZTProxy proxy services are not supported for use in mainland China. Use only lawful, authorized targets.
Next steps
Send one authorized request, confirm the observed exit, then save the configuration only on a trusted device. Never put real proxy credentials into a shared collection, screenshot, or exported environment.