Postman is the most popular API testing platform with a visual interface and CLI runner. Configure KnoxProxy in Postman to test APIs from different geographic locations, verify geo-fenced endpoints, and debug region-specific API responses without deploying test infrastructure.
In Postman desktop, go to Settings (gear icon) > Proxy. Enable "Use custom proxy configuration".
// Postman GUI path:
// Settings > Proxy > Use custom proxy configuration
// Proxy Server: gw.knoxproxy.com
// Port: 7000
// Check both HTTP and HTTPSIn the same proxy settings panel, enable "Proxy requires authentication" and enter your KnoxProxy credentials.
// Proxy Auth:
// Username: USER
// Password: PASSTo target a specific country, append the country code to the username field.
// Username: USER-country-jp
// This routes all Postman requests through a Japanese IPSend a GET request to httpbin.org/ip to verify the proxy is working.
GET https://httpbin.org/ip
// Expected response:
// { "origin": "x.x.x.x" } <-- KnoxProxy exit IPFor CI/CD pipelines, use Newman with proxy environment variables.
HTTP_PROXY=http://USER:PASS@gw.knoxproxy.com:7000 \
HTTPS_PROXY=http://USER:PASS@gw.knoxproxy.com:7000 \
newman run collection.jsonTarget a specific country in Newman by changing the proxy username.
HTTP_PROXY=http://USER-country-au:PASS@gw.knoxproxy.com:7000 \
HTTPS_PROXY=http://USER-country-au:PASS@gw.knoxproxy.com:7000 \
newman run collection.json --reporters cli,json#!/bin/bash
# Run Postman collection through KnoxProxy via Newman
# Basic proxy routing
HTTP_PROXY=http://USER:PASS@gw.knoxproxy.com:7000 \
HTTPS_PROXY=http://USER:PASS@gw.knoxproxy.com:7000 \
newman run my-collection.json \
--environment production.json \
--reporters cli,json \
--reporter-json-export results.json
# Country-targeted run (Germany)
HTTP_PROXY=http://USER-country-de:PASS@gw.knoxproxy.com:7000 \
HTTPS_PROXY=http://USER-country-de:PASS@gw.knoxproxy.com:7000 \
newman run my-collection.json \
--environment production.json \
--folder "Geo Tests"Each Postman request opens a new connection and gets a fresh proxy IP. For sticky sessions, use USER-session-{id} in the proxy username field to maintain the same IP across a collection run.
| Problem | Fix |
|---|---|
| Error: connect ECONNREFUSED | Verify proxy is enabled in Settings > Proxy. Check that gw.knoxproxy.com:7000 is reachable. |
| 407 Proxy Authentication Required | Enable "Proxy requires authentication" and verify username and password. For Newman, check env var format. |
USER-country-de-city-berlin-session-profile07Order matters -- geo flags before the session flag. The session name is free text; use the profile ID so the mapping is self-documenting. Password stays as issued; no flags belong there. HTTP on :7000, SOCKS5 on :7001, same credentials.
Yes. Postman has a built-in proxy configuration panel under Settings > Proxy with username/password fields.
Yes. Newman inherits HTTP_PROXY and HTTPS_PROXY environment variables. Set them in your CI pipeline configuration.
When enabled, the proxy routes all Postman requests. Use the "Proxy Bypass" list to exclude specific domains.
In the GUI, update the proxy username before each request. In Newman, run separate commands with different proxy usernames.
Free trial on rotating residential -- 2 minutes setup, no credit card.