Proxies for Postman

Before you start

You need an active plan, your gateway credentials from the dashboard, and either your server IP whitelisted or a user and password pair. Replace USER:PASS in the examples with your real credentials.

The rotating port gives a new IP on every request. Sticky ports hold one address for the life of the session, and both live on the same host, so you choose by port rather than by product.

The gotcha worth knowing

Postman applies the proxy to the whole application, including its own telemetry calls. If you only want specific requests proxied, drive them from a pre-request script or use a separate workspace.

Configuration

Postman sets proxies globally in settings rather than per request, so the change applies to every call in the workspace.

Open Settings, then the Proxy tab. Turn on Add a custom proxy configuration and enter:

Proxy Type:  HTTP and HTTPS
Proxy Server: gateway.proxyrotator.com
Port:         11000
Proxy auth:   on
Username:     USER
Password:     PASS

Under the General tab, turn off SSL certificate verification only if you are seeing certificate errors through the proxy and you understand what that disables.

Where to go next

Running more than one tool against the same gateway is normal. These cover the others.

• All integration guides, setup notes for every tool we cover
• Guides and tutorials, the concepts behind the config, including when to rotate and when not to
• Apify setup, another library or framework wired to the same gateway
• n8n setup, another library or framework wired to the same gateway
• Rotating proxies, a new IP per request, which is the default for crawling