---
search:
  tags:
    - Library placements
    - DELETE
seo:
  description: >-
    Deletes a Placement of your organization, and removes it from every…
    Reference for the DELETE /library/placements/{placementId} endpoint in the
    AdCrunch API.
sidebar:
  label: Delete a Placement
  badge: DELETE
title: Delete a Placement
type: openapi-operation
---
Deletes a Placement of your organization, and removes it from every group that holds it. The groups stay. A global Placement cannot be deleted: it answers `404`. A Placement that a live Variation names cannot be deleted: it answers `409`.

`DELETE /library/placements/{placementId}`

**Responses**

- `200` — The Placement is gone.
- `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 \`library:write\`. \`error\` is \`forbidden\`.
- `404` — No Placement of your organization with that id. A global Placement answers this too, because only AdCrunch changes one. \`error\` is \`not\_found\`. So a second delete answers \`404\`.
- `409` — A live Variation names the Placement, and nothing changed. Remove the Variation or change its Placement, then delete again. \`error\` is \`placement\_in\_use\`.

Response example, 200:

```json
{
  "ok": true
}
```
