---
title: "Delete a collection"
method: DELETE
path: "/cms/collections/{collectionId}"
tags: ["CMS collections"]
---

# Delete a collection

`DELETE /cms/collections/{collectionId}`

## Request

- Base URL: `https://api.cactal.ai/v1`
- URL: `https://api.cactal.ai/v1/cms/collections/{collectionId}`
- Auth: HTTP bearer

Soft-deletes the collection, making it and all of its items unreachable through the API; the slug becomes reusable. Refused with a conflict while any reference field in another collection targets this collection — delete those fields first. If the website has a published version, the deletion is validated against the published site’s content queries and rejected when the site still depends on the collection.

## Path parameters

- `collectionId` string, required

## Response `200`

Deletion acknowledgement.

- object
  - `deleted` true, required: Always `true` once the collection is deleted.

## Other responses

- `400`: Validation failed. The response `message` names the first invalid field.
- `401`: Missing, invalid, expired, or revoked API key.
- `403`: The authenticated principal lacks the required capability.
- `404`: The resource does not exist or is outside the principal’s access scope.
- `409`: The request conflicts with the current state of the resource.
- `429`: Rate limit exceeded. Retry after the number of seconds in the `Retry-After` header.

---

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