Launch a draft. This is the call that spends: it creates the campaign at DelivrDSP, and where your account funds campaigns in advance it reserves the campaign's budget.

Needs the campaigns:write scope, like every campaign write.

Send no body. A campaign created through this API already carries every launch setting, so change settings with Update campaign before launching.

Checked before anything happens, each answering 400 naming the problem:

• The campaign has a budget.
• A campaign targeting audiences names at least one.
• Each audience is in the campaign's project, has finished building (Completed), is not paused, and is a people audience: a company audience has no identifiers a campaign can reach.

On success the answer is 202 with status activating. Delivr then creates the campaign at DelivrDSP, prepares and attaches each audience, and turns the campaign on. Poll Get campaign until status is active; delivery reads scheduled before the start date and live once spending. Draft creatives on the campaign become active at launch. A campaign with no creative it can serve stays activating, so add one before or after launching.

If setup fails, status becomes blocked with a reason: setup_failed (the failure was on Delivr's side), action_required (DelivrDSP refused something you can change; decline_reason says what), or unknown. A campaign whose launch failed before it reached DelivrDSP can be launched again. Launching anything other than a draft or such a failed launch answers 409, so a retried request never creates a second campaign.