---
type: api
title: Bulk update monitors
description: **Spaces method and path for this operation:**
url: https://www.elastic.co/elastic/docs-builder/docs/4371/api/doc/kibana/operation/operation-put-synthetic-monitors-bulk-update
resource: https://www.elastic.co/elastic/docs-builder/docs/4371/api/doc/kibana/operation/operation-put-synthetic-monitors-bulk-update
products:
  - Kibana
---

# Bulk update monitors

Availability: 9.5+

- Server: `https://{kibana_url}`

## Paths

- `PUT` `/api/synthetics/monitors/_bulk_update`
- `PUT` `/s/{space_id}/api/synthetics/monitors/_bulk_update`

- [Api key auth](/elastic/docs-builder/docs/4371/api/doc/kibana/authentication#apikeyauth)
- [Basic auth](/elastic/docs-builder/docs/4371/api/doc/kibana/authentication#basicauth)

## Description

Refer to [Spaces](https://www.elastic.co/docs/deploy-manage/manage-spaces) for more information.

Partially update multiple monitors in a single request.
Each `updates` entry has its own `id` and `attributes` patch, so one request can apply a different change per monitor. Unspecified fields are left unchanged. Patches use the same merge, validate, and encrypt path as `PUT /api/synthetics/monitors/{id}`.
For private-location monitors, Fleet is synced once for the batch instead of once per monitor.
You must have `all` privileges for the Synthetics feature in the Observability section of the Kibana feature privileges.
This is a versioned public API (`elastic-api-version: 2023-10-31`).

## Request Body

`application/json`

- `updates` ([] object · min: 1 · max: 1000) — required
  Monitors to update. Minimum 1 entry, maximum 1000. Each `id` may appear at most once. `attributes` must contain at least one field.
  - `attributes` (object) — required
    Attributes to update for the monitor. You can specify the same fields as in `PUT /api/synthetics/monitors/{id}`. An empty object is rejected.
  - `id` (string · min: 1 · max: 1024) — required
    The monitor config ID to update.

## Responses

#### `200`

A successful response. The `result` array is in request order. Per-id failures (not found, validation, Fleet sync) set `updated: false` and `error` without failing the whole batch. `errors` is present only when there are service-level sync errors.

`application/json`

- `errors` ([] object)
  Optional service-level errors from the bulk sync.
- `result` ([] object)
  - `error` (string)
    Present when `updated` is `false`.
  - `id` (string)
    The monitor config ID from the request.
  - `updated` (boolean)
    If `true`, the monitor was updated. If `false`, see `error`.
#### `400`

Bad request. Returned when `updates` is missing or empty, an `attributes` object is empty, or the same `id` appears more than once.

## Code Examples

#### Console

```console
PUT /api/synthetics/monitors/_bulk_update
{
  "updates": [
    {
      "id": "monitor1-id",
      "attributes": {
        "enabled": false
      }
    },
    {
      "id": "monitor2-id",
      "attributes": {
        "tags": ["bulk-patched"]
      }
    },
    {
      "id": "monitor3-id",
      "attributes": {
        "schedule": {
          "number": "15",
          "unit": "m"
        }
      }
    }
  ]
}
```

#### curl

```curl
curl -X PUT "https://{kibana_url}/api/synthetics/monitors/_bulk_update" \
  -H "Content-Type: application/json" \
  -d '{
  "updates": [
    {
      "id": "monitor1-id",
      "attributes": {
        "enabled": false
      }
    },
    {
      "id": "monitor2-id",
      "attributes": {
        "tags": ["bulk-patched"]
      }
    },
    {
      "id": "monitor3-id",
      "attributes": {
        "schedule": {
          "number": "15",
          "unit": "m"
        }
      }
    }
  ]
}'
```

## Response Examples

#### Bulk update response example1

A response from a bulk update with one failure.

```json
{
  "result": [
    {
      "id": "monitor1-id",
      "updated": true
    },
    {
      "id": "missing-id",
      "updated": false,
      "error": "Monitor id missing-id not found!"
    },
    {
      "id": "monitor3-id",
      "updated": true
    }
  ]
}
```