# Delete a message template

Removes one template for good. Refused while a draft or an automation rule still points at it — the answer names what is still using it. To retire a template without breaking those, patch it with `isActive: false` instead, which takes it out of the picker and keeps it readable.

Access class: `workspace`.

## Endpoint

`DELETE /v1/message-templates/{id}`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| id | path | string | Yes |
| body | query | null | No |
| params | query | object | No |
| query | query | object | No |

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "deleted": true
  }
}
```

### default

a refusal: `{"error": "<what a person needs to read>"}`. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.

Content type: `application/json`.

```json
{
  "error": "string"
}
```