Test geo-aware APIs
Point Postman at a country-targeted ProxyOmega username and confirm how an endpoint responds to callers in the US, Germany, or anywhere else, all without leaving your desk.
Integration Proxy manager
Postman Integration
Postman is the standard workbench for building and testing APIs, and it can send every request through a proxy you define. This guide covers enabling Postman's custom proxy configuration, entering a ProxyOmega host and port, adding username and password authentication, and verifying the route. Menu paths match the current Postman desktop app.
- 200+countries
- 1.5M+residential IPs
- HTTP/HTTPSrequest routing
Postman
What is Postman?
Postman is a desktop and web application for designing, sending, and testing API requests. Developers and QA teams use it to build collections of requests, script tests, manage environments, and inspect responses. It is one of the most widely used tools in API development, and it includes a built-in proxy setting so requests can egress from an address other than your own.
Postman's own proxy configuration is an HTTP-style forward proxy: you give it a host, a port, and optional credentials, and it sends your API requests through that server. This is distinct from Postman's separate capability to act as a capturing proxy for inspecting traffic; here we are configuring Postman as a client that routes outbound requests through ProxyOmega.
Routing Postman through a residential proxy is useful when an API is geo-restricted, rate-limits by IP, or behaves differently depending on where the caller appears to be. Instead of your office or datacenter IP, the API sees a residential address in the location you choose. The proxy setting is global to the app, so it applies to every request across all your collections until you turn it back off, which is worth keeping in mind when you switch between proxied and direct testing.
Postman
Why pair Postman with residential proxies
Postman decides which requests to send; ProxyOmega decides what IP the API sees when they arrive. For anyone testing location-aware endpoints or working around per-IP limits, that pairing turns Postman into a tool that can call an API from effectively anywhere.
Work around per-IP limits
When an API throttles by source IP, routing through rotating residential addresses gives your test runs fresh IPs instead of hammering the endpoint from one.
Realistic caller identity
ProxyOmega residential IPs read as ordinary consumer traffic, so an API that treats datacenter ranges differently sees your requests the way it would see a real user.
Postman
How to add ProxyOmega to Postman
From the ProxyOmega dashboard, note your username with any targeting parameters and your account API key, which acts as the password. Then enable Postman's custom proxy.
- Open Postman and go to Settings from the gear icon in the top-right (or the Postman menu).
- Select the Proxy tab.
- Turn on Use custom proxy configuration.
- Under Proxy type, leave HTTP and HTTPS selected so both request types are routed.
- In Proxy server, enter your plan's endpoint, for example residential.proxyomega.com, and in the port field enter a port from your plan's range such as 10000.
- Tick This proxy requires authentication.
- Enter your Username with any targeting parameters, for example youruser-country-us, and your Password, which is the dashboard API key.
- Close settings. If prompted, save and restart Postman so the proxy takes effect.
- Send a request to a service such as https://ipinfo.io/json and confirm the returned IP and country reflect the proxy.
- If your APIs use HTTPS with the proxy and you hit certificate warnings, review Postman's SSL certificate verification setting under Settings, General.
Postman
Choosing a protocol and a plan
Postman's custom proxy configuration is HTTP-based, and it applies to both HTTP and HTTPS requests, which covers essentially all API testing. You do not need to think about SOCKS5 here; every ProxyOmega port also serves HTTP and HTTPS on the same port, so the endpoint and port you enter work directly with Postman's proxy field. Keep both HTTP and HTTPS request types ticked unless you have a reason to route only one.
Pick the plan based on the endpoints you are calling and how they treat different IP types.
| Workload | Plan | Why |
|---|---|---|
| General API testing, rotating IPs | Budget Unlimited | Fresh residential IP per port; -country-xx targets a country |
| High-volume test runs | Premium Unlimited | Higher-speed residential on premium.proxyomega.com:8000 |
| City, state, or ASN targeting, pay per GB | Platinum | Precise geo control on platinum.proxyomega.com:20228 |
| Endpoints that key off mobile networks | Mobile | Real 4G/5G IPs on mobile.proxyomega.com:20229 |
| A fixed IP to whitelist with an API | Static ISP | Stable US IP (Dallas) on isp.proxyomega.com, ports 30000-30099 |
Postman
Troubleshooting
When Postman requests fail through the proxy, the cause is usually authentication, the username suffix, TLS verification, or the source IP. The Postman Console (View, then Show Postman Console) shows the underlying error for each request.
Connection refused / 407
A 407 Proxy Authentication Required means the credentials were rejected. Confirm the password is your dashboard API key rather than your login password, and that the username's targeting parameters are valid, since an unsupported parameter returns 407 as well. If you authenticate by IP whitelist instead, note that once any IP is whitelisted only those IPs may connect, so the machine running Postman must be on the list.
SSL / certificate errors
If HTTPS requests fail with certificate errors only when the proxy is on, check Settings, then General, for SSL certificate verification. Adjust it for your test environment, and make sure the target's own certificate chain is valid.
Proxy setting seems ignored
Postman may need a restart for a new proxy to apply. Also confirm no higher-priority system or environment proxy is overriding the custom setting, and that Use custom proxy configuration is actually toggled on rather than left on the default.
FAQ
Frequently asked questions
Where is the proxy setting in Postman?
Open Settings from the gear icon, choose the Proxy tab, and turn on Use custom proxy configuration. Enter the ProxyOmega host and port, tick This proxy requires authentication, and add your username and API-key password.
Does Postman work with SOCKS5?
Postman's custom proxy configuration is HTTP-based and routes both HTTP and HTTPS requests, which is all you need. Every ProxyOmega port also serves HTTP and HTTPS, so you use the same endpoint and port in Postman's proxy field.
What is my proxy password for Postman?
It is the account API key shown in your ProxyOmega dashboard, not your website login password. The username is your account username plus any dash-separated targeting parameters.
How do I make Postman call an API from another country?
Append -country- and a two-letter code to your username, such as youruser-country-de. Postman will then route requests through a residential IP in that country. Add -session- and -ttl- for a sticky IP across a test run.
Why do I get certificate errors only through the proxy?
HTTPS interception and verification settings can trip on proxied requests. Check SSL certificate verification under Settings then General, and confirm the target endpoint presents a valid certificate. The Postman Console shows the exact TLS error.
Do I need to restart Postman after changing the proxy?
Often yes. If a new proxy configuration does not seem to apply, save the setting and restart Postman, and make sure no system or environment proxy is overriding your custom configuration.
Test APIs from any location Start routing today.
Route Postman requests through ProxyOmega residential IPs.
ProxyOmega