OpenAPI 3.1.02026-08-215701892.2 MB

15e893e69e8c

Ad Campaigns

Pause or resume a campaign

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.

put/v1/ads/campaigns/{campaignId}/status

Path parameters

campaignIdstring required

Platform campaign ID

Request body

status'active' | 'paused' required
platform'facebook' | 'instagram' | 'tiktok' | 'linkedin' | 'pinterest' | 'google' | 'twitter' | 'openai' required

Response

Campaign status updated

status'active' | 'paused'

The status written to the campaign

updatedinteger

Number of ads whose own stored status changed too. 0 is normal on a resume whose ads are all awaiting the platform.

skippedinteger

Number of ads whose own status was left as it was

skippedReasonsstring[]

Why each group of ads was skipped