This feature is available on Postman Enterprise plans. For more information, see the pricing page.
For added governance and security, you can configure a runner to route HTTP and HTTPS traffic generated during monitor runs through a proxy server that enforces outbound request policies. This helps inspect outbound traffic and ensure a runner communicates only with approved destinations.
You can route traffic through an external proxy server your organization already uses. Or, use Postman’s built-in proxy server if you don’t want to create and maintain your own.
When you start a runner using the Postman CLI, you can route outbound HTTP and HTTPS traffic through either an external proxy server or Postman’s built-in proxy server.
To use an external proxy server, specify the proxy server URL when starting a runner. To use the built-in proxy server, configure an authorization service that determines which outbound requests are allowed or blocked.
You can also specify custom CA certificates if required by your proxy server or authorization service.
Learn more at Configure a runner to route traffic through a proxy server.
With Postman’s built-in proxy server, you can control outbound requests from a runner using an authorization service that you configure. Create the authorization service and define rules that determine which requests are allowed or blocked. Once the authorization service is deployed and running, you can start a runner using the built-in proxy server.
Learn more at Start a runner with the built-in proxy server.