Skip to main content
Each page below documents a single campaign operation — request, parameters, response shape, and errors. A platform-managed campaign starts as DRAFT, then attaches products/creatives and executes into media buys. For the conceptual model — fields, lifecycle, media buys, and packages — see the Campaign overview. Directed campaigns use the same create/update/list resource but have no DRAFT planning or execute step. Their separately gated connect → subscribe → list products → create/update → reconcile flow is grouped below.

Manage

Create campaign

POST /campaigns — open a new DRAFT campaign

Get campaign

GET /campaigns/:id — full resource with creative coverage

List campaigns

GET /campaigns — compact summaries, filterable

Update campaign

PUT /campaigns/:id — partial updates and media-buy actions

Delete campaign

DELETE /campaigns/:id — archive the campaign

Lifecycle

Execute campaign

POST /campaigns/:id/execute — launch into media buys

Pause campaign

POST /campaigns/:id/pause — halt spend across media buys

Reactivate campaign

POST /campaigns/:id/reactivate — resume a PAUSED campaign

Products

Auto-select products

POST /campaigns/:id/auto-select-products — let Scope3 pick a set

Get campaign products

GET /campaigns/:id/products — list the selected products

Status

Get media buy status

GET /campaigns/:id/media-buy-status — live ADCP status

Directed campaigns (alpha)

Subscribe account

Start the one-to-one account mirror

List provider products

Read exact product and pricing-option IDs for a directed write

Read subscription health

Inspect sync freshness and the metadata-history boundary

Read delivery

Fetch delivery live from the connected provider