***

title: Monitor internal APIs with runners
approved: 2025-11-03T00:00:00.000Z
slug: docs/monitoring-your-api/runners/overview
max-toc-depth: 2
ux: v12
topictype: concept
------------------

<Info class="plan">
  This feature is available on Postman Enterprise plans. For more information, see the [pricing page](https://www.postman.com/pricing/).
</Info>

With Private API Monitoring, you can run monitors on runners in your own network to test your organization's APIs, without exposing them to the public internet.

To get started, create a runner in your Postman team and use the Postman CLI to set it up in your internal network. Once set up, the runner securely polls Postman for monitor runs from your internal network, following your organization's internal routing and access controls. The runner then sends the results to the Postman cloud.

## Configure a runner in your team

Create a runner to monitor and test your organization's internal APIs. You can create a runner when you configure a monitor or from **Runner** settings. Once you start a runner from your internal network, your teammates can select the runner when creating monitors and check the health and performance of internal APIs from Postman.

Learn more at [Configure runners for internal APIs](/docs/monitoring-your-api/runners/configure-a-runner/).

## Set up a runner in your restricted network

Once you've created a runner in your team, use the Postman CLI to set it up in your internal network. Get started by learning how to start and configure a runner. To set up a runner in your cloud network, such as a virtual private cloud, you can learn how to containerize a runner using Docker.

Learn more at [Set up a runner in your restricted network](/docs/monitoring-your-api/runners/set-up-a-runner-in-your-network/).

## Configure a runner to use a proxy server

For extra governance and security, you can configure your runner to use a proxy server that routes traffic and evaluates requests.

If your organization has an existing proxy server, you can specify its URL when you start the runner. You can also use the built-in proxy server if you don't want to create and maintain your own. To use the built-in proxy server, you need to set up an authorization service with rules that decide which requests from the runner are allowed or blocked. If your proxy service or authorization service require custom CA certificates, you can also specify the path to the file.

Learn more at [Set up a runner to use a proxy server](/docs/monitoring-your-api/runners/proxy-server/overview/).

## Manage runners in your team

View and manage all of your team's runners when you configure a monitor. You can view the commands for starting a runner with the Postman CLI, update your runners, delete runners you no longer need, and more. You can also manage runners from **Runner** settings where you can view more details about your runners, like their health status.

Learn more at [Manage runners for internal APIs](/docs/monitoring-your-api/runners/manage-runners/).

## Troubleshoot runners

To learn how to troubleshoot runners in your internal network, see [Troubleshoot runners in Postman](/docs/monitoring-your-api/runners/troubleshoot-runners/).