Pause or resume a campaign
Pauses or resumes a campaign, leaving the on/off switches of its ad sets and ads as they are.
Writes the campaign's own on/off switch and nothing else, on every platform (Meta, TikTok, Google, LinkedIn campaign group, Pinterest, X, ChatGPT (OpenAI)). Its ad sets and ads keep their own switches: pausing stops their delivery through the campaign, and resuming lets each of them deliver again only if its own switch is on. An ad set or ad you paused individually stays paused; resume it with PUT /v1/ads/ad-sets/{adSetId}/status or PUT /v1/ads/{adId}/status. See the Status model in the Ad Campaigns tag.
Live read, then write. The campaign's switch is read from the platform first. When that live read shows it already in the requested state nothing is written (updated: 0, skipped: 1, with the reason). Otherwise the switch is written (updated: 1), read back and stored, and the delivery status of the ads under it (up to 20) is re-read and stored, so an immediate GET returns what the platform now reports. A stored switch never skips a write, and when the platform cannot be read the write always goes out. On Meta the check reads the campaign's own status, so a delivery status such as IN_PROCESS or WITH_ISSUES does not force a write.
Request
- Base URL: https://zernio.com/api
- URL: https://zernio.com/api/v1/ads/campaigns/{campaignId}/status
- Auth: HTTP bearer
Path parameters
Platform campaign ID
Request body
Response
Campaign status updated