Type to search.

Bulk activate alerts

Base URL
https://{kibana_url}
  • POST /api/alerting/v2/alerts/_bulk_activate
  • POST /s/{space_id}/api/alerting/v2/alerts/_bulk_activate
Auth The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability Planned We plan to add this functionality in a future Elastic Stack update. Subject to changes. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

Create the same action for multiple alerts in a single request.

Required privileges

Privileges manage_alerting-v2-alerts

Path parameters

space_id string optional

An identifier for the space. If space_id is not provided in the URL, the default space is used. Refer to Spaces for more information.

Header parameters

kbn-xsrf string required

A required header to protect against CSRF attacks

Request body

items object[] · min items: 1 · max items: 100 required

List of 1 to 100 activate actions to create, each for a different alert_id.

alert_id string · min length: 1 · max length: 150 required

Identifier of the alert to apply the action to.

reason string · min length: 1 · max length: 1024 required

Reason for activating the alert.

Responses

Returns the number of created actions and per-item errors for actions that were not created.

application/json
affected_count integer · min: 0 · max: 9007199254740991 required

Number of resources the operation successfully touched.

errors object[] required

Errors encountered during the operation.

error object required
code string required

Stable error code you can branch on, for example INVALID_SCHEDULE or RULE_ALREADY_EXISTS.

details map string to object

Optional structured context whose keys depend on code. Identifier keys such as rule_id, action_policy_id and group_hash are stable, permanent public identifiers. On a 400 request-validation error, details.source (params, query, or body) names the failing part and is the only guaranteed key. The sibling details.errors may change. Do not branch on it.

message string required

A readable explanation of the error. The wording can change without notice. Do not parse this field.

id string required

The identifier of the resource that failed.