---
search:
  tags:
    - Campaign Plans
    - POST
seo:
  description: >-
    Creates a Campaign Plan. A Campaign Plan is the AdCrunch planning document.
    It… Reference for the POST /context/campaign-plans endpoint in the AdCrunch
    API.
sidebar:
  label: Create a Campaign Plan
  badge: POST
title: Create a Campaign Plan
type: openapi-operation
---
Creates a Campaign Plan. A Campaign Plan is the AdCrunch planning document. It is **not** a provider campaign. For provider campaigns, see the entities in the Observe API.

Only a name, a description and a currency are necessary. You write the window, the budget envelope and the Brand one part at a time. Write each amount in whole units of the currency: `40.5` is €40.50.

The new plan starts in draft. The answer is `409` if the slug already exists in your organization.

`POST /context/campaign-plans`

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

- `body` (string) — The long document of the Campaign Plan (markdown): the argument for the split, how success will be judged, and anything else a reviewer reads. It is what a person approves.
- `brand_name` (string) — The Brand's slug. Optional and re-pointable — a Campaign Plan may precede its brand or cover a portfolio. Addressed by slug because that is the handle every Context surface uses; the Campaign Plan stores the id.
- `currency` (string, required) — ISO 4217. Editable while no Line Item carries a budget or a cost target (\`cpa\`, \`cpc\` or \`cpm\`), frozen thereafter.
- `description` (string, required) — One-line summary — what a reader picks this Campaign Plan by.
- `end_date` (string) — Omit for an always-on plan. Line Items inherit this.
- `name` (string, required) — Display name.
- `slug` (string) — Optional explicit slug handle; normalized to kebab-case. Defaults to one derived from the name.
- `start_date` (string)
- `total_budget` (number) — The envelope: what we have. Omit for "no declared constraint" — which is not the same as zero.

Request body example:

```json
{
  "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",
  "currency": "EUR",
  "description": "The spring sale of Acme, on Meta, in France and Belgium.",
  "end_date": "2026-05-31",
  "name": "Spring Sale 2026",
  "slug": "spring-sale",
  "start_date": "2026-03-01",
  "total_budget": 5000
}
```

**Responses**

- `201` — The Campaign Plan as created, in \`draft\`, at \`revision\` 1, with no rows. \`allocation.allocated\` is 0 and \`unallocated\` is the whole envelope.
- `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` — \`brand\_name\` names no Brand in this organization. \`error\` is \`not\_found\`. Despite its name the field takes a Brand \*\*slug\*\*.
- `409` — Another Campaign Plan already holds that slug. \`error\` is \`slug\_conflict\`.
- `422` — Four codes share this status. \`invalid\_slug\`; \`invalid\_currency\` (it must be a three-letter ISO 4217 code); \`invalid\_amount\` (an amount has no more decimals than its currency, and is never negative); \`invalid\_window\` (the end precedes the start).

Response example, 201:

```json
{
  "allocation": {
    "allocated": 0,
    "comparable": true,
    "unallocated": 5000,
    "unit": null
  },
  "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": 0,
  "name": "Spring Sale 2026",
  "revision": 1,
  "slug": "spring-sale",
  "startDate": "2026-03-01",
  "status": "draft",
  "totalBudget": 5000,
  "updatedAt": null
}
```
