curl proxy setup
Use an HTTP or SOCKS5 proxy with curl: -x, credentials, socks5h, environment variables, .curlrc and an exit check.
How to send Postman requests through a proxy: where the Proxy tab is, the difference between the system proxy and a custom proxy, where to type the address, username and password, how the web app differs, and how to check the exit. Step by step, in plain words.
A proxy is another computer that sends your requests to the internet for you; the server you call then sees the proxy's address instead of yours.
The system proxy is the proxy already set in Windows, macOS or Linux; many programs read it. A custom proxy is one you type into Postman itself.
HOST and PORT are the address of the proxy computer and the number of its door. USERNAME and PASSWORD prove that you may use it.
Operating-system proxy settings are in a separate guide, and curl has its own. This one is only about the Postman Proxy tab. A proxy changes the network exit of your API calls and nothing else: the API's own keys, limits and terms stay as they are.
In the Postman desktop app click the Settings icon in the header, click Settings, then choose the Proxy tab.
The Postman pages say Use system proxy and Respect HTTP_PROXY, HTTPS_PROXY and NO_PROXY environment variables are on by default. With them on, Postman takes the proxy from your operating system or from those environment variables, not from fields you type.
Use the system proxy when the computer is already set up and you want Postman to follow it. Use a custom proxy when only Postman should go through a particular proxy. To switch, turn off the system proxy and the environment-variable option, then turn on Use custom proxy configuration.
If both the system proxy and the custom proxy are on, Postman uses the custom proxy.
Under Proxy configurations for sending requests choose HTTP, HTTPS or both. Both are selected by default.
Pick the protocol from the list (HTTP, SOCKS5, SOCKS5H, SOCKS4 or SOCKS4A), then type the address and port. Do not add http:// in front: the protocol is already chosen in the list.
If the proxy needs a username and password, turn on the Proxy auth toggle and enter Username and Password. The page calls this basic authentication.
Optional, the last field of the custom section. A comma-separated list of hosts that go directly and skip the custom proxy, for example a local test server.
Postman lists SOCKS5 among the protocols but says it sends only HTTP and HTTPS requests through a SOCKS proxy. For ordinary API calls HTTP is the simplest choice. Proxy302 can issue either protocol when you generate a proxy.
The Proxy tab also has a Default proxy configuration section. The documentation says the desktop app uses the operating system's proxy by default and that you only need this section if that proxy requires a username and password: tick This proxy requires authentication, enter them and click Save and Restart Postman. It names a restart only for this option; it does not say whether the custom proxy fields need one, so if the change does not seem to apply, restart Postman yourself.
The documentation says you cannot configure the default proxy in the Postman web app. The web app sends requests through an agent. The Desktop Agent is a local application that sends requests through your local machine and network; the Cloud Agent sends them through Postman's cloud servers and cannot reach private or local resources. The pages I read do not say how a proxy applies to each agent, so for a proxy that you control use the desktop app and check the result as shown below.
Create a request, set the method to GET, enter https://ipinfo.io/json and click Send.
The body shows the IP, country and network that the site sees. If the IP is the proxy's and not yours, the proxy is in use. The guide on checking a proxy's IP, country and ISP explains the fields.
Test the same details with curl. If curl fails too, the problem is the proxy details, not Postman.
GET https://ipinfo.io/jsonEnter this in the Postman address bar with the method set to GET. Run it once with the custom proxy off and once with it on and compare the ip field.
• Requests fail and your network needs a proxy. The documentation says to turn on Use system proxy and check that the proxy is set in the operating system.
• Requests fail and your network does not need a proxy. Turn off both Use system proxy and Use custom proxy configuration.
• The settings seem to be ignored. The documentation says that when HTTP_PROXY or HTTPS_PROXY variables exist, Postman uses the system proxy and ignores its own proxy settings; remove them from your shell or system, or start Postman from a script that clears them.
• 407 Proxy Authentication Required. The proxy rejected the username or password. Retype or copy them again from My assets.
For API tests that need a particular country, rotating residential traffic is billed per GB and the exit country is set when you generate the proxy. If you want one address that does not change, a static ISP IP stays fixed for the whole lease. HTTP is on port 2222 and SOCKS5 on port 3333 of proxy.proxy302.com.
Open the rotating residential page, choose the line and the country, keep Protocol on HTTP, then click Review cost and generate.
Open My assets and copy HOST, PORT, USERNAME and PASSWORD. The Connect page shows a ready example with your own details.
In Postman fill in the custom proxy as shown above: protocol HTTP, your address and port, Proxy auth on.
Send GET https://ipinfo.io/json and read the country and org fields.
From mainland China, start the helper tool from the Connect page first and keep it open while you use the proxy.
The Budget line costs US$1.50 per GB, US$1.35 per GB in a 100 GB package and US$1.20 per GB at 300 GB. There is no free trial, and the smallest purchase is 1 GB. Which exit locations are available changes daily.
Click the Settings icon in the header, then Settings, then the Proxy tab.
The system proxy is the one set in your operating system. A custom proxy is typed into Postman. If both are on, Postman uses the custom proxy.
The documentation says you cannot configure the default proxy there. For a proxy you control, use the desktop app.
It lists SOCKS5 among the protocols, but only for HTTP and HTTPS requests. HTTP is the simplest choice.
Type them, separated by commas, into the last field of the custom proxy section (hosts that skip the proxy).
Official documentation · Confirmed on:
Read on 2 November 2026: Settings, Proxy tab; Default proxy configuration with a credentials checkbox and Save and Restart Postman; Use system proxy; Use custom proxy configuration with Use proxy for, Proxy server protocol list (HTTP, SOCKS5, SOCKS5H, SOCKS4, SOCKS4A), Proxy auth and a field for hosts that skip the proxy; the custom proxy wins when both are on; SOCKS only for HTTP and HTTPS requests; troubleshooting with environment variables.
The page does not describe the Postman Console, the web app's proxy field step by step or a connection test.
Official documentation · Confirmed on:
Read on 2 November 2026: the Proxy tab; Use system proxy and Respect HTTP_PROXY, HTTPS_PROXY and NO_PROXY environment variables are on by default; turn both off and turn on Use custom proxy configuration to use another proxy.
The page covers only the start of the Proxy tab.
Official documentation · Confirmed on:
Read on 2 November 2026: Desktop, Cloud, Browser and Interceptor agents and what each sends; the Desktop Agent sends requests through the local machine and network, the Cloud Agent cannot reach private or local resources.
The page does not mention proxies or proxy configuration.
Product observation · Confirmed on:
Product facts file of the site (checked against the console, the backend and the price table on 18-19 October 2026): prices in US$ (1 PTC = US$1), protocols and ports, no free trial.
Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.