---
title: "Pause or resume a campaign"
method: PUT
path: "/v1/ads/campaigns/{campaignId}/status"
tags: ["Ad Campaigns"]
---

# Pause or resume a campaign

`PUT /v1/ads/campaigns/{campaignId}/status`

Writes the campaign's own on/off switch, then lets the platform cascade delivery to its ad sets and ads.
Makes one platform API call, not one per ad.

The switch is always written, whatever delivery status the ads underneath report: an ad still in review
does not block resuming its campaign. The echoed `status` is the confirmation that it landed.

`updated` / `skipped` describe only the ads whose own stored status CHANGED alongside it, so
`updated: 0` is a normal successful response, not a no-op. Ads are skipped when they are in a terminal
status (rejected, completed, cancelled), already in the target state, or switched on but not yet
delivering — the last group keeps its `pending_review` / `error` status until the platform reports what
it became. `skippedReasons` names which case applies.

On Meta this flips the campaign only. An ad set paused in its own right stays paused, so pair this with
PUT /v1/ads/ad-sets/{adSetId}/status when you also need the ad set switched back on.

## Path parameters

- `campaignId` string, required

## Request body

- object
  - `status` 'active' | 'paused', required
  - `platform` 'facebook' | 'instagram' | 'tiktok' | 'linkedin' | 'pinterest' | 'google' | 'twitter' | 'openai', required

## Response `200`

Campaign status updated

- object
  - `status` 'active' | 'paused' — The status written to the campaign
  - `updated` integer — Number of ads whose own stored status changed too. 0 is normal on a resume whose ads are all awaiting the platform.
  - `skipped` integer — Number of ads whose own status was left as it was
  - `skippedReasons` string[] — Why each group of ads was skipped

## Other responses

- `400` — Invalid input or campaign spans multiple social accounts
- `401` — Unauthorized
- `404` — No ads found for this campaign

---

[API](https://skmtc.net/zernio/apis/zernio-api.md) · [All operations](https://skmtc.net/zernio/apis/zernio-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/zernio/zernio-api/revisions/3c7cf84cec44/schema)