---
search:
  tags:
    - Campaign Plans
    - DELETE
seo:
  description: >-
    Deletes a Campaign Plan and its Line Items. Send the base_revision you…
    Reference for the DELETE /context/campaign-plans/{slug} endpoint in the
    AdCrunch API.
sidebar:
  label: Delete a Campaign Plan
  badge: DELETE
title: Delete a Campaign Plan
type: openapi-operation
---
Deletes a Campaign Plan and its Line Items. Send the `base_revision` you read. The slug becomes free again.

AdCrunch **keeps** the record of what those lines already created. Those provider objects are live in an ad account, and the deletion of a planning row does not remove them.

The answer is `409` with `error=revision_mismatch` if the Campaign Plan changed after you read it.

`DELETE /context/campaign-plans/{slug}`

**Responses**

- `204` — Deleted, with its Line Items. What those lines already created is \*\*kept\*\*: those provider objects are live in somebody’s ad account and were never ours to withdraw.
- `400` — The request does not match the schema of this operation: a field is missing or has the wrong type, or the body is not valid JSON. \`error\` is \`invalid\_request\`, and \`issues\` names each field. Nothing was changed.
- `401` — No API key, or one that does not resolve. See the security scheme. \`error\` is \`unauthorized\`.
- `402` — The organization has no active subscription. An owner subscribes at \`paywallUrl\`. \`error\` is \`organization\_unentitled\`.
- `403` — The caller does not hold \`campaign\_plan:write\`. \`error\` is \`forbidden\`.
- `404` — No Campaign Plan with that slug. \`error\` is \`not\_found\`.
- `409` — The plan moved since you read it. \`error\` is \`revision\_mismatch\`. Adding or deleting a Line Item moves an \*\*approved\*\* plan, because it takes the approval away. Re-read the Campaign Plan before you delete it.
