---
title: "Enable per-action limits"
type: reference
method: POST
path: /rest-api/per-action/limits/{type}/{entityId}/enable.do
tag: "Limits"
---

# Enable per-action limits

`POST https://YOUR-NETWORK-DOMAIN/rest-api/per-action/limits/{type}/{entityId}/enable.do`

Switches per-action conversion limits on for an advertiser, campaign or banner. The limits added through /per-action/add/limit only cap delivery while this switch is on. Requires the MANAGE_CAPPING_AND_LIMITATIONS and CAMPAIGN_ACTION_LIMIT permissions and UPDATE access to the owning advertiser. Only ADVERTISER, CAMPAIGN and BANNER are accepted; other types return 400.

## Path params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `type` | string | yes | `CAMPAIGN` | Type of the entity: ADVERTISER, CAMPAIGN or BANNER |
| `entityId` | integer | yes | `2001` | Unique numeric identifier of the entity |

## Responses

- `200` — Per-action limits enabled; actionLimitsEnabled echoes the new state
- `400` — Unsupported entity type or malformed ID
- `401` — Authentication error
- `403` — Not enough permissions
- `404` — Entity not found or deleted

## Example request

```bash
curl --request POST \
  --url 'https://YOUR-NETWORK-DOMAIN/rest-api/per-action/limits/CAMPAIGN/2001/enable.do' \
  --header 'X-Api-Key: YOUR_API_KEY'
```

Source: https://epom.com/ad-server/docs/api/limits/post-per-action-limits-enable