---
title: "Acknowledge an alert"
method: POST
path: "/api/alerting/v2/alerts/{group_hash}/_ack"
tags: ["alerting-v2"]
---

# Acknowledge an alert

`POST /api/alerting/v2/alerts/{group_hash}/_ack`

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

<div><span class="operation-verb post">post</span>&nbsp;<span class="operation-path">/s/{space_id}/api/alerting/v2/alerts/{group_hash}/_ack</span></div>

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

Create an action for a specific alert group.<br/><br/>[Required authorization] Route required privileges: manage_alerting-v2-alerts.

## Path parameters

- `group_hash` string, required

## Headers

- `kbn-xsrf` string, required

## Request body

- KibanaHTTPAPIsAlertingNewAckAlertAction
  - `episode_id` string, required — The episode identifier for the alert to acknowledge.

## Response `204`

Returns the newly created alert action.

## Other responses

- `400` — Indicates an invalid schema or parameters.
- `401` — Indicates the request was not authenticated.
- `403` — Indicates the user does not have the required privileges to perform the request.
- `404` — Indicates the alert event was not found.
- `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)