Spotify Ads API — Draft Campaign Management

Build, review, and publish campaign hierarchies using the draft workflow. Drafts are staging versions of campaigns, ad sets, and ads that can be created, edited, validated, and published as a batch — nothing goes live until you explicitly publish.

Why Drafts

The draft flow is the preferred way to create campaigns because:

• Review before going live — build the entire hierarchy, then validate and publish in one step
• Batch validation — the validate action checks the entire campaign hierarchy (campaign + ad sets + ads) at once, surfacing all errors before anything is created
• Safe iteration — edit any part of the draft hierarchy without affecting live entities
• Undo-friendly — delete drafts at any time before publishing; no cleanup of live entities needed
• Incomplete data allowed — drafts accept partial entities (e.g., an AUDIO ad without companion_asset_id). Required fields are only enforced during VALIDATE or PUBLISH, so you can build the hierarchy incrementally

The alternative (direct entity creation via /campaigns, /ad_sets, /ads) validates at each individual API call, so errors in later entities (e.g., ads) are discovered only after the campaign and ad sets are already live. Prefer the draft flow for any new campaign creation.