---
title: "Get a rule change-history event"
method: GET
path: "/api/alerting/v2/rules/{id}/history/{eventId}"
tags: ["alerting-v2"]
---

# Get a rule change-history event

`GET /api/alerting/v2/rules/{id}/history/{eventId}`

**Spaces method and path for this operation:**

<div><span class="operation-verb get">get</span>&nbsp;<span class="operation-path">/s/{space_id}/api/alerting/v2/rules/{id}/history/{eventId}</span></div>

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

Get the full detail for a single rule change-history event, including the rule configuration snapshot.<br/><br/>[Required authorization] Route required privileges: read_alerting-v2-rules.

## Path parameters

- `id` string, required
- `eventId` string, required

## Response `200`

Returns the requested rule change-history event.

- object
  - `action` string, required
  - `actor` object, required
    - `name` string, required
    - `profileId` string
  - `changes` object
    - `count` integer, required
    - `summary` object
  - `comment` string
  - `id` string, required
  - `isCurrent` boolean
  - `metadata` object
  - `reason` string
  - `snapshot` object, required
  - `tags` string[]
  - `timestamp` string, required

## Other responses

- `400` — Indicates the request failed schema validation.
- `401` — Indicates the request was not authenticated.
- `403` — Indicates the user does not have the required privileges to perform the request.
- `404` — Indicates a change-history event with the given ID does not exist.
- `500` — Indicates an unexpected server-side error.
- `503` — Indicates the alerting engine is disabled by the `alerting:v2:enabled` advanced setting.

---

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