Back to Integrations
Tutorial 8 Min Read

How to Configure Proxy Settings in Postman

Learn how to route your API requests, integration tests, and collection runs through Turbo Proxy SOCKS5/HTTP servers inside Postman.

API requests testing panel and rotating proxy gateway mapping

1. Postman & API Proxies

Postman is the leading API client and platform for developer testing. When building, testing, or debugging APIs, developers often need to send requests from specific geolocations, bypass region-based IP restrictions, or test rate-limiting thresholds.

By default, Postman routes your API requests directly through your local internet connection. To test your endpoints from other regions or simulate client traffic, you must configure Postman to route outgoing requests through proxy servers.

Integrating **Turbo Proxy** SOCKS5 or HTTP gateways into Postman allows you to run collection tests, debug REST/GraphQL calls, and audit geofenced headers using clean residential IPs.


2. Setting Up Global Proxy in Postman

Follow these settings to configure global proxy routing in Postman:

Step 1: Open Settings

Launch Postman. Click the **gear icon** in the top-right corner of the window and select Settings.

Step 2: Go to the Proxy Tab

Select the Proxy tab from the settings navigation bar.

Step 3: Enable Global Proxy

Under the **Global Proxy Configuration** section, check the box next to "Send requests through a global proxy".

Step 4: Input Proxy Settings

Enter your connection details:

  • Proxy Server: gate.turboproxy.online
  • Port: e.g., 7000
  • Proxy Type: Check HTTP or HTTPS.
  • Proxy Auth: Toggle on **"Proxy requires authentication"**. Enter your proxy username and password credentials.

Click Save and close the settings window. Postman will route all requests through the proxy.


3. Custom Proxy Rules in Postman

If you do not want to route all outgoing requests globally through the proxy, you can set up **System Proxy** settings or define target exception rules using the **Bypass** configurations.

In the Proxy tab of Postman, find the "Bypass proxy for" text field. You can input comma-separated IP addresses or domains (e.g., localhost, 127.0.0.1, internal-api.local) that should run on your direct network connection.


Troubleshooting Common Connection Issues

1. Error: "Could not send request" (SSL/Certificate validation fails)

When routing through proxies, target servers might return SSL verification errors. To bypass this during testing, go to **Settings** > **General** inside Postman and toggle **"SSL certificate verification"** to Off.

2. HTTP 407 Proxy Authentication Required

Double-check that the credentials entered under "Proxy requires authentication" match your dashboard credentials. Make sure you don't have leading or trailing spaces.

Frequently Asked Questions

Does Postman support SOCKS5 proxies?
Postman's built-in proxy settings only support HTTP/HTTPS proxies. For SOCKS5, use a system-level tool like Proxifier to tunnel Postman's traffic through a SOCKS5 proxy, or use the Postman CLI (newman) with an http-proxy-agent.
Will the proxy apply to all Postman collections?
Yes. When a Global Proxy is configured in Postman Settings, it applies to all requests and collection runs across all workspaces unless overridden by request-level proxy settings or a bypass rule.
Can I bypass the proxy for specific domains in Postman?
Yes. In the Proxy settings tab, use the 'Bypass proxy for' field and enter a comma-separated list of hostnames or IP addresses (e.g., localhost, 127.0.0.1) to exclude from proxy routing.
Why is Postman showing SSL verification errors through a proxy?
SSL certificate verification errors can occur when routing through HTTP proxies. Temporarily disable SSL verification in Settings → General for testing only. Re-enable it in production environments.

Automate API Auditing

Ready to route your automated collection tests through clean residential and mobile IPs? Register today.

Get Turbo Proxies