---
title: "Delete an automation"
method: DELETE
path: "/api/v1/automations/{id}"
tags: ["automations"]
---

# Delete an automation

`DELETE /api/v1/automations/{id}`

## Request

- Base URL: `https://app.blueticked.com`
- URL: `https://app.blueticked.com/api/v1/automations/{id}`
- Auth: HTTP bearer

Tidy up after yourself: remove an automation your own key created.

A key can only delete automations that KEY created. Anything else answers `not_found`, the same as an id that never existed. Whether another integration owns something here is not your key's business.

Paused only. A live automation returns 409 `resource_in_use`: pause it with `PATCH { enabled: false }` first, so customer replies never go quiet as a side effect of a cleanup script.

The automation stops immediately (every trigger path skips deleted flows and outstanding waits are cancelled), while its past runs stay on record, so the history explaining a message you sent last week survives.

## Path parameters

- `id` string, required

## Response `200`

Success

- object
  - `ok` boolean, required
  - `deleted` object, required
    - `id` string, uuid, required
    - `name` string, required
    - `was_live` boolean, required

## Other responses

- `400`: Validation failed
- `401`: Unauthorized: missing or invalid API key
- `402`: Insufficient wallet balance
- `403`: Forbidden: scope, plan limit, or suspension
- `404`: Not found
- `409`: Conflict (idempotency-key reuse or resource in use)
- `422`: Understood but refused: the request is well-formed, the action is not permitted for this resource
- `429`: Rate limited
- `500`: Internal error
- `502`: An upstream provider refused or failed the request
- `503`: Channel or send queue unavailable

---

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