---
title: "Delete a rule"
method: DELETE
path: "/api/alerting/v2/rules/{id}"
tags: ["alerting-v2"]
---

# Delete a rule

`DELETE /api/alerting/v2/rules/{id}`

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

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

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

[Required authorization] Route required privileges: manage_alerting-v2-rules.

## Path parameters

- `id` string, required

## Headers

- `kbn-xsrf` string, required

## Response `204`

The rule was deleted successfully.

## 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 rule 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/c36ed1cbdbb5/schema)