WeProxy Proxy Setup For Postman

Postman Desktop can use the system proxy setting or define a custom proxy for Postman requests only. If you want to use WeProxy for API testing without affecting other apps, custom proxy configuration gives you more control.

The external proxy setting Postman uses to send requests is not the same as Postman’s built-in proxy for capturing incoming traffic. This guide covers the external WeProxy connection.

Settings✕

GeneralThemesShortcutsDataCertificatesProxyUpdateAbout

Use the system proxy

Use custom proxy configuration

Proxy type✓HTTP✓HTTPS

Proxy server

gw.weproxy.com.tr8989

Proxy auth

Username

USER

Password

••••••••

Required WeProxy Details

Configuring a Custom Proxy in Postman

1. Open the Postman Desktop app.
2. Click the Settings icon in the header, then select Settings.
3. Go to the Proxy tab.
4. Enable Use custom proxy configuration.
5. Under Use proxy for, choose whether HTTP and/or HTTPS requests should go through the proxy.
6. Set the proxy type to HTTP or SOCKS, depending on your WeProxy product.
7. In Proxy server, enter only the host, without an http:// or socks5:// prefix.
8. Enter your WeProxy port in the port field.
9. If a username and password are required, turn on Proxy auth and enter your credentials.
10. To exclude addresses from the proxy, list them in Proxy bypass, separated by commas.

When the custom proxy is enabled, it takes precedence over the system proxy setting. To avoid confusion, keep only the method you need enabled.

Using the System Proxy Setting

If you have already configured WeProxy system-wide on Windows or macOS:

1. In Postman, open Settings > Proxy.
2. Enable Use system proxy.
3. Turn off Use custom proxy configuration.
4. If the system proxy requires authentication, enter the username and password in Default proxy configuration.
5. Save and restart Postman.

Testing a Request

Create a new GET request:

https://api.ipify.org?format=json

Click Send. The response should show your WeProxy exit IP. You can then test your actual API endpoint.

Postman Proxy Errors

407 Proxy Authentication Required

Check the Proxy auth setting and your credentials. Make sure the host field doesn't include a protocol.

Postman uses the system proxy instead of the custom proxy

According to the Postman docs, the custom proxy takes precedence when it's enabled. To keep things simple, turn off the option you aren't using and restart Postman.

Requests fail through a SOCKS proxy

Postman routes HTTP and HTTPS requests through a SOCKS proxy. Confirm that the SOCKS version you selected matches your WeProxy product.

SSL certificate error

Instead of permanently disabling certificate verification, check the certificate chains of the proxy and the destination server. If a corporate CA is required, add the trusted CA file in Postman’s certificate settings.

Source

• Postman Docs: Configuring a proxy server