---
title: "Delete an escalation policy"
method: DELETE
path: "/api/v1/escalation-policies/{escalation_policy}"
tags: ["Escalation policies"]
---

# Delete an escalation policy

`DELETE /api/v1/escalation-policies/{escalation_policy}`

## Request

- Base URL: `https://wardenpoint.com` (the document declares no server; this is the origin it was published from)
- URL: `https://wardenpoint.com/api/v1/escalation-policies/{escalation_policy}`
- Auth: API key in header `X-API-Key`

Deletes the policy — but only while nothing points at it. A policy some recipient or group still uses answers 409 with the list of who uses it, and stays. That refusal is deliberate: detaching would not break the setting, it would silently EMPTY its ladder — the account-wide floor is a single message with no timeout step, so an unanswered call would be repeated by nobody and handed to nobody. Repeating the call on an already-deleted policy returns 404.

## Path parameters

- `escalation_policy` string, uuid, required

## Response `204`

Deleted.

## Other responses

- `401`: API key missing, invalid, revoked or expired.
- `403`: API key lacks the config.write ability, or the policy belongs to another company.
- `404`: No policy with this UUID.
- `409`: Something still points at it, so it was NOT deleted. The body carries `code: ENTITY_IN_USE` and a `references` list — each entry names what holds it (`type`, `uuid`, `name`, and sometimes a `detail` like «2 shifts»). Detach it there and repeat; there is no force flag.

---

[API](https://skmtc.dev/wardenpoint/apis/wardenpoint-api.md) · [All operations](https://skmtc.dev/wardenpoint/apis/wardenpoint-api/llms.txt) · [OpenAPI document](https://skmtc.dev/wardenpoint/apis/wardenpoint-api/revisions/259ee445728e?raw)