---
title: "Enable campaign rules"
type: reference
method: POST
path: /rest-api/rules/campaign/{campaignId}/enable.do
tag: "Targeting Rules"
---

# Enable campaign rules

`POST https://YOUR-NETWORK-DOMAIN/rest-api/rules/campaign/{campaignId}/enable.do`

Activates the targeting rules engine for the specified campaign, allowing its configured rule groups to take effect during ad serving. The campaign is identified by its numeric ID in the URL path. The response is a JSON object with 'success: true' on success. Requires the caller to have UPDATE permission on the campaign's advertiser share and CAMPAIGN_RULES_MANAGEMENT permission. The action is logged for audit purposes. POST only: a GET answers 405, since a state change over GET can be triggered by a prefetch or an embedded link.

## Path params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `campaignId` | integer | yes | `1234` | The unique numeric identifier of the campaign whose targeting rules should be enabled |

## Responses

- `200` — Rules enabled successfully
- `400` — Bad request — invalid or missing parameters
- `401` — Unauthorized - authentication error
- `403` — Forbidden - insufficient permissions
- `404` — Campaign not found

## Example request

```bash
curl --request POST \
  --url 'https://YOUR-NETWORK-DOMAIN/rest-api/rules/campaign/1234/enable.do' \
  --header 'X-Api-Key: YOUR_API_KEY'
```

Source: https://epom.com/ad-server/docs/api/targeting-rules/post-rules-campaign-enable