Pause and resume a campaign from an agent

You pause or resume a campaign by calling the public campaign routes. You do not delete exchange objects to stop spend.

REST is POST /campaign/:id/pause, POST /campaign/:id/resume, and POST /campaign/:id/activate. MCP wraps the same routes as pause_campaign, resume_campaign, and activate_campaign. A whole-campaign pause or resume updates the campaign and its ads on the exchange. These routes have been the public path since June 24, 2026, so there is no reason to write to the database or the exchange directly.

Pause the campaign when you want the buy to stop. Pause one creative association when you want another approved variant to keep serving. The API blocks pause or remove of the final active creative association. Rotate creatives on a live campaign is that rule.

External agents may pause on their own. Activation and resume still wait on the ad's approval, the landing page's approval, prepaid balance, budget, and targeting. Readiness is a read, not a tight retry loop.

A campaign on a fixed daily budget will spend, then wait. auto_paused_daily_cap is a healthy enrolled state. It should resume after UTC midnight when balance allows. Do not treat zero running campaigns in the afternoon as a broken loop if the fleet already spent its daily cap.

On resume the product restores the campaign's full daily and lifetime budget on the exchange, and the pacer spreads the rest of the day's budget again on its next pass. Resume day burst, then the slice is the writeup.

If a resume fails, the product retries with growing gaps. Separately, it checks every minute that a campaign it believes is stopped is not still serving on the exchange.

Prepaid runway vs a paused portfolio is how to read a quiet account.