> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/reference/remote-access-and-apis/api-examples/get-monitor.md).

# Get Monitor

Retrieve typed monitor definitions by UUID through the v2 batch-read API.

### Endpoint

**POST** `/api/v2/monitors/batch/read`

Use this endpoint for one UUID or several. The v2 API has no single-monitor GET route. These routes require a backend with the monitors-v2 capability enabled; otherwise they return `404`.

For a backend without v2, use **GET** `/api/monitors/{uuid}` to retrieve YAML, or `/api/monitors/{uuid}/details` for a JSON response containing the YAML string. See the [legacy read examples](https://docs.groundcover.com/reference/remote-access-and-apis/api-examples/legacy-monitor-reads.md#read-a-definition) for authentication and response details.

### Authentication

Use an [API key](https://docs.groundcover.com/administer/api-keys.md) with at least Viewer (`read`) permissions. Include `Authorization: Bearer <YOUR_API_KEY>`, `X-Backend-Id: <YOUR_BACKEND_ID>`, and `Content-Type: application/json`.

### Request Body

`monitorUUIDs` is a required, non-empty array of monitor UUIDs. Use [List Monitors](https://docs.groundcover.com/reference/remote-access-and-apis/api-examples/list-monitors.md) to find them.

```bash
curl --request POST 'https://api.groundcover.com/api/v2/monitors/batch/read' \
  --header 'Authorization: Bearer <YOUR_API_KEY>' \
  --header 'X-Backend-Id: <YOUR_BACKEND_ID>' \
  --header 'Content-Type: application/json' \
  --data '{
  "monitorUUIDs": [
    "00000000-0000-4000-8000-000000000001"
  ]
}'
```

### Response

HTTP `200` returns:

* `fetchedCount` and `failedCount`: the number of successful and failed reads.
* `monitors`: an object keyed by UUID. Each value contains `uuid`, `backendId`, timestamps, origin/provisioning metadata, and the typed JSON `spec`.
* `errors`: per-ID errors for unknown, deleted, or out-of-scope monitors.

Inspect `failedCount` and `errors` even when HTTP status is `200`. The `spec` includes `name`, `type`, `isPaused`, evaluation settings, `issueDisplay`, `notificationSettings`, and `model`.

See [Monitors v2 API](https://docs.groundcover.com/reference/remote-access-and-apis/api-examples/monitors-v2-api.md) for the complete definition example and for updating, pausing, deleting, or exporting monitors. To inspect evaluation results, use [Monitor Issues API](https://docs.groundcover.com/reference/remote-access-and-apis/api-examples/monitor-issues-api.md) or [Query Monitors Summary](https://docs.groundcover.com/reference/remote-access-and-apis/api-examples/query-monitors-summary.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.groundcover.com/reference/remote-access-and-apis/api-examples/get-monitor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
