Update the API key of rules in bulk by ID

Base URL
https://{kibana_url}
  • POST /api/alerting/v2/rules/_bulk_update_api_key
  • POST /s/{space_id}/api/alerting/v2/rules/_bulk_update_api_key
Auth

Rotates each rule executor task API key to one derived from the current user’s credentials.

Required privileges

Privileges manage_alerting-v2-rules

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

ids string[] · min items: 1 · max items: 100 required

Explicit list of IDs to operate on. Each id can appear at most once.

Responses

Returns the result of the bulk update API key operation.

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.

Base URL
https://{kibana_url}