Create a DelivrDSP campaign from what you want it to do: a goal, audiences, budget, flight and bid. Delivr composes the DelivrDSP settings from that (the bid range, contracted terms, end date and pacing) the same way the dashboard's campaign wizard does.
The campaign is always created as a draft. Nothing is sent to DelivrDSP and nothing spends until you call Launch campaign. The worked example is Launch a DelivrDSP Campaign with the API.
Needs the campaigns:write scope. Every campaign write needs this scope on your API key, separately from read access. A key without it is refused with 403 and required_scopes: ["campaigns:write"]. Contact support to enable it for your key.
The project must have a DelivrDSP integration. It is looked up from project_id, so the body does not name one.
Money (budget, daily_budget, the bid fields, contracted and fine_tune.monthly_budget) is in your account's dollars, the same dollars the campaign reads report.
Unknown fields are refused with 400 naming the field, so a misspelled key is never silently dropped. Other refusals also name the field and the problem, in a plain-text body. The missing-scope 403 is the one JSON refusal.
Add ?dry_run=true to compose without storing anything: the answer is 200 with the draft that would be created.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
401Missing or invalid authentication.
