---
search:
  tags:
    - Line Items
    - DELETE
seo:
  description: >-
    Takes a Creative off one… Reference for the DELETE
    /context/campaign-plans/{slug}/line-items/{lineItemId}/creatives/{creativeId}
    endpoint in the AdCrunch API.
sidebar:
  label: Remove a Creative from a Line Item
  badge: DELETE
title: Remove a Creative from a Line Item
type: openapi-operation
---
Takes a Creative off one Line Item. The Creative stays in the pool of the Campaign Plan, and on each other Line Item that uses it.

To take the Creative out of the plan, use `DELETE /campaign-plans/{slug}/creatives/{creativeId}`. Removing a Creative that the Line Item does not use changes nothing. The call does not change the revision or the status of the Campaign Plan or of a Line Item. A validated Line Item stays validated.

`DELETE /context/campaign-plans/{slug}/line-items/{lineItemId}/creatives/{creativeId}`

**Responses**

- `200` — The Creatives of the Line Item after the call, oldest first.
- `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 such Campaign Plan, or no Line Item with that id on it. \`error\` is \`not\_found\`.

Response example, 200:

```json
{
  "creatives": []
}
```
