---
title: "Delete cappings by IDs"
type: reference
method: POST
path: /rest-api/capping/delete.do
tag: "Capping"
---

# Delete cappings by IDs

`POST https://YOUR-NETWORK-DOMAIN/rest-api/capping/delete.do`

Permanently deletes one or more capping objects, identified by pairs of capping ID and capping type. Each element in the ids array must be a colon-separated string in the format 'capping_id:capping_type' (e.g. '123:CAMPAIGN_FREQUENCY', '456:PLACEMENT_CLICKS'). The capping type is required because capping IDs are only unique within one capping type. Requires UPDATE permission on the entity each capping belongs to, and MANAGE_INVENTORY_CAPPING (placement cappings) or MANAGE_CAPPING_AND_LIMITATIONS (the others) enabled; when one id is refused, nothing is deleted.

## Form params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `ids` | array<string> | yes | `123:CAMPAIGN_FREQUENCY` | Array of colon-separated 'capping_id:capping_type' pairs to delete (e.g. '123:CAMPAIGN_FREQUENCY', '456:PLACEMENT_CLICKS') |

## Responses

- `200` — Cappings deleted successfully
- `400` — An id is not in the id:TYPE format, or names an unknown capping type; the message says which
- `401` — Authentication error
- `403` — The caller may not change the entity one of the cappings belongs to
- `404` — One of the ids is not a capping of the given type

## Example request

```bash
curl --request POST \
  --url 'https://YOUR-NETWORK-DOMAIN/rest-api/capping/delete.do' \
  --header 'X-Api-Key: YOUR_API_KEY' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data-urlencode 'ids=123:CAMPAIGN_FREQUENCY'
```

Source: https://epom.com/ad-server/docs/api/capping/post-capping-delete