Pause or resume many campaigns
Pauses or resumes up to 50 campaigns in one call, with a separate result per campaign so one failure does not block the rest.
Each campaign is updated
concurrently and the response contains a per-campaign result so a
single bad row does not fail the whole batch. Each campaign is read,
written and re-read exactly as PUT /v1/ads/campaigns/{campaignId}/status
describes: only the campaign's own switch is written, never its ad sets'
or ads'. updated / skipped count campaigns.
Authorization
bearerAuth API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.adcampaigns.bulkUpdateAdCampaignStatus({ body: { status: 'active', campaigns: [ { platformCampaignId: 'platformcampaign_abc123', platform: 'facebook', }, ], },});console.log(data);{ "status": "active", "totals": { "updated": 0, "skipped": 0, "failed": 0 }, "results": [ { "platformCampaignId": "string", "platform": "string", "updated": 0, "skipped": 0, "platformCampaignStatus": "string", "error": "string" } ]}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.
List campaign assets
Lists the sitelinks, callouts and other assets attached directly to a Google campaign. Fresh reads are cached for 10 minutes; exhausted quota may return the last successful read with stale=true. Inherited assets are not included.