Postman Proxy Setup

Postman is the most popular API testing tool for developers, and it supports HTTP proxy configuration natively. Using Hex Proxies with Postman lets you test APIs from different geographic locations, verify regional responses, debug geo-restricted endpoints, and validate proxy credentials before integrating into production code.

Configuring the Custom Proxy

1. Open Postman and go to **Settings** (gear icon) > **Proxy**
2. Toggle **Use custom proxy configuration** to ON
3. Set **Proxy Type** to HTTP
4. Enter the proxy server details:
5. - **Proxy Server**: `gate.hexproxies.com`
6. - **Proxy Port**: `8080`
7. Toggle **Proxy Auth** to ON and enter your Hex Proxies username and password
8. Ensure both **HTTP** and **HTTPS** are checked

Verifying Proxy Connectivity

Send a GET request to `https://httpbin.org/ip` to confirm traffic routes through the proxy. The response should show a residential IP address, not your machine's IP.

{
  "origin": "203.0.113.42"
}

Using Environment Variables for Proxy Credentials

Store proxy credentials in Postman environment variables to avoid hardcoding them:

• Create variables: `proxy_user` and `proxy_pass`
• Reference them in Pre-request Scripts:

// Pre-request Script to set proxy auth header
pm.request.headers.add({
    key: 'Proxy-Authorization',
    value: 'Basic ' + btoa(pm.environment.get('proxy_user')
        + ':' + pm.environment.get('proxy_pass'))
});

Geo-Targeted Testing

To test API responses from specific countries, modify the proxy username to include a country code. In Postman's proxy username field, enter: `your-username-country-us` for US IPs, `your-username-country-gb` for UK IPs, etc.

Common Pitfalls

Postman's proxy settings apply globally — all requests in all collections route through the proxy when enabled. Toggle the proxy off when you need direct access. If you see SSL certificate errors, ensure you are connecting to the proxy over HTTP (not HTTPS) — the proxy handles the TLS connection to the target.

When to Use Postman with Proxies

• Quick connectivity validation — verify proxy credentials work before writing code
• Regional API debugging — test how APIs respond from different countries
• Geo-restriction testing — check which endpoints are accessible from specific regions
• Pre-integration testing — confirm proxy configuration before implementing in your application
• Team collaboration — share proxy-configured collections with team members for consistent testing