Apple is killing its campaign management API. Developers have until January 2027 to move on

Apple quietly confirmed that its Campaign Management API, the programmatic backbone developers and marketers have used for years to run App Store ad campaigns, will stop working on January 26, 2027. The replacement is a new Ads Platform API, and Apple wants everyone migrated as early as possible.

The news surfaced through preview documentation Apple published under the name Apple Ads Platform API Preview Release Notes, which lays out what’s changing, what’s new, and how the two APIs differ. Developer Aaron Perris flagged the transition publicly, but the details come straight from Apple.

Apple has announced that the "Apple Ads Campaign Management API" will be sunset on January 26, 2027.

The new Apple Ads Platform API will be coming in Summer 2026. pic.twitter.com/ZyNDi77vDL
— Aaron (@aaronp613) April 3, 2026

The new API covers Apple Maps ads too, not just the App Store

The Campaign Management API, currently at version 5, handled everything from campaign creation to performance reporting for App Store ads. The new Ads Platform API takes over all of that, but with a broader scope. It will also support Apple Maps ads, a category the old API never touched.

Your Complete iOS 26 Playbook:

Get our exclusive Ultimate iOS 26 Guide 📚 — absolutely FREE when you sign up for our newsletter below.

Apple is characteristically sparse on migration specifics in this first preview release, but the documentation does include side-by-side comparisons of how requests and responses differ between the two APIs, notes on new and expanded features, and updated tooling guidance. It’s a starting point, not a complete migration handbook.

After January 26, 2027, the old API simply stops working

The hard deadline is real. After that date, the Campaign Management API will stop functioning entirely. No campaign management, no reporting. If you’re still on it when that date hits, your workflows go dark.

For teams running automated ad operations at scale, the sooner this migration gets prioritized, the better. Apple’s advice to move “as early as possible” isn’t just boilerplate. API transitions at this scope take time to test and validate, and a hard cutoff with no fallback leaves no room for a last-minute scramble.