Change a campaign's settings. The body is a JSON merge patch in the same fields as Create campaign: a field you leave out keeps its value, a field you send replaces it, and null clears it. Delivr recomposes whatever the change affects, so changing budget also moves what is derived from it.
Needs the campaigns:write scope, like every campaign write.
A draft is only stored. A launched campaign's change is sent to DelivrDSP first and stored only once DelivrDSP accepts it, so a failure there changes nothing. Raising a launched campaign's budget is funded first, like a launch. Two changes are refused on a launched campaign with 409: changing its audiences (DelivrDSP keeps serving the lists attached at launch), and clearing with null a field DelivrDSP cannot clear (the refusal names it). daily_budget can be cleared.
Add ?dry_run=true to see the change without making it: the answer is 200 with the campaign as it would be and changes, the fields that would move.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Missing or invalid authentication.
Campaign not found, or not in the key's organization.
DelivrDSP could not apply the change to a launched campaign. Nothing was stored.