---
title: "Monitors search"
method: GET
path: "/api/v1/monitor/search"
tags: ["Monitors"]
---

# Monitors search

`GET /api/v1/monitor/search`

Search and filter your monitors details.

## Query parameters

- `query` string
- `page` integer
- `per_page` integer
- `sort` string

## Response `200`

OK

- MonitorSearchResponse — The response from a monitor search.
  - `counts` MonitorSearchResponseCounts — The counts of monitors per different criteria.
    - `muted` MonitorSearchCountItem[] — Search facets.
      - `count` integer — The number of found monitors with the listed value.
      - `name` unknown
    - `status` MonitorSearchCountItem[] — Search facets.
      - `count` integer — The number of found monitors with the listed value.
      - `name` unknown
    - `tag` MonitorSearchCountItem[] — Search facets.
      - `count` integer — The number of found monitors with the listed value.
      - `name` unknown
    - `type` MonitorSearchCountItem[] — Search facets.
      - `count` integer — The number of found monitors with the listed value.
      - `name` unknown
  - `metadata` MonitorSearchResponseMetadata — Metadata about the response.
    - `page` integer — The page to start paginating from.
    - `page_count` integer — The number of pages.
    - `per_page` integer — The number of monitors to return per page.
    - `total_count` integer — The total number of monitors.
  - `monitors` MonitorSearchResult[] — The list of found monitors.
    - `classification` string — Classification of the monitor.
    - `creator` Creator — Object describing the creator of the shared element.
      - `email` string — Email of the creator.
      - `handle` string — Handle of the creator.
      - `name` string, nullable — Name of the creator.
    - `id` integer — ID of the monitor.
    - `last_triggered_ts` integer, nullable — Latest timestamp the monitor triggered.
    - `metrics` string[] — Metrics used by the monitor.
    - `name` string — The monitor name.
    - `notifications` MonitorSearchResultNotification[] — The notification triggered by the monitor.
      - `handle` string — The email address that received the notification.
      - `name` string — The username receiving the notification
    - `org_id` integer — The ID of the organization.
    - `quality_issues` string[] — Quality issues detected with the monitor.
    - `query` string — The monitor query.
    - `scopes` string[] — The scope(s) to which the downtime applies, for example `host:app2`. Provide multiple scopes as a comma-separated list, for example `env:dev,env:prod`. The resulting downtime applies to sources that matches ALL provided scopes (that is `env:dev AND env:prod`), NOT any of them.
    - `status` 'Alert' | 'Ignored' | 'No Data' | 'OK' | 'Skipped' | 'Unknown' | 'Warn' — The different states your monitor can be in.
    - `tags` string[] — Tags associated with the monitor.
    - `type` 'composite' | 'event alert' | 'log alert' | 'metric alert' | 'process alert' | 'query alert' | 'rum alert' | 'service check' | 'synthetics alert' | 'trace-analytics alert' | 'slo alert' | 'event-v2 alert' | 'audit alert' | 'ci-pipelines alert' | 'ci-tests alert' | 'error-tracking alert' | 'database-monitoring alert' | 'network-performance alert' | 'cost alert' | 'data-quality alert' | 'network-path alert' | 'data-jobs alert' — The type of the monitor. For more information about `type`, see the [monitor options](https://docs.datadoghq.com/monitors/guide/monitor_api_options/) docs.

## Other responses

- `400` — Bad Request
- `403` — Forbidden
- `429` — Too many requests

---

[API](https://skmtc.net/datadog/apis/api-v1.md) · [All operations](https://skmtc.net/datadog/apis/api-v1/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/datadog/api-v1/revisions/ca5871004d26/schema)