---
search:
  tags:
    - Campaign Plans
    - POST
seo:
  description: >-
    Approves a Campaign Plan and validates its draft Line Items. An… Reference
    for the POST /context/campaign-plans/{slug}/approve endpoint in the AdCrunch
    API.
sidebar:
  label: Approve a Campaign Plan
  badge: POST
title: Approve a Campaign Plan
type: openapi-operation
---
Approves a Campaign Plan and validates its draft Line Items. An approval records that a person agreed to the content of the Campaign Plan. It is a record, not a gate: the provider write tools do not check it.

**This call blocks on nothing.** You can approve a Campaign Plan with no budget, with more allocated than the envelope, or with parts missing. The person who approves decides. To check one Line Item before you build it, read its readiness.

This call creates nothing and spends nothing. To build a Line Item, use the mutation tools with the `mutation:write` permission.

This call moves the `revision` of the Campaign Plan, and the `revision` of each Line Item it validates. Read the Campaign Plan again before your next guarded write.

A Line Item that you add after the approval starts in draft, and it puts the Campaign Plan back into draft. The answer is `409` with `error=revision_mismatch` if the Campaign Plan changed after you read it.

`POST /context/campaign-plans/{slug}/approve`

**Request body** (`application/json`, required)

- `base_revision` (integer, required) — The revision last read via GET. This is what makes it an approval \*\*of the content that was read\*\*, rather than of whatever the row holds now.

Request body example:

```json
{
  "base_revision": 2
}
```

**Responses**

- `200` — The approved Campaign Plan, and how many Line Items this call validated. A Line Item that was already validated is not counted. \*\*Approving spends nothing and creates nothing\*\* — it records the approval of a person. The provider write tools do not check it. Building goes through the mutation tools on \`mutation:write\`.
- `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 Campaign Plan with that slug. \`error\` is \`not\_found\`.
- `409` — The plan moved since you read it. \`error\` is \`revision\_mismatch\`. This is what makes the call an approval \*\*of the content you read\*\*, rather than of whatever the row holds now.

Response example, 200:

```json
{
  "campaignPlan": {
    "allocation": {
      "allocated": 2500,
      "comparable": true,
      "unallocated": 2500,
      "unit": "total"
    },
    "assignees": [
      {
        "id": "usr_4d8b12",
        "name": "Maya Lindqvist"
      }
    ],
    "body": "## Why this split\n\nMeta carries the reach. One Line Item keeps the budget in one place.\n\n## How it will be judged\n\nRevenue in the window, against the spring of 2025.",
    "brand": {
      "name": "Acme",
      "slug": "acme"
    },
    "brandId": "brd_6a9c33",
    "commentCount": 2,
    "createdAt": 1768435200000,
    "createdBy": "usr_5d2b71",
    "currency": "EUR",
    "description": "The spring sale of Acme, on Meta, in France and Belgium.",
    "endDate": "2026-05-31",
    "id": "cpl_4e1a08",
    "lineItemCount": 1,
    "name": "Spring Sale 2026",
    "revision": 3,
    "slug": "spring-sale",
    "startDate": "2026-03-01",
    "status": "approved",
    "totalBudget": 5000,
    "updatedAt": 1769040000000
  },
  "lineItemsValidated": 1
}
```
