Apple Ads Campaign Management API v5 shuts down on January 26, 2027

Apple will shut down the Apple Ads Campaign Management API v5 on January 26, 2027. After that date, scripts and tools that still call v5 will stop working. The replacement is the Apple Ads Platform API. If you or any tool you pay for manages Apple Ads campaigns or pulls ad reports through the API, plan the move before mid January.

What Apple announced

Apple's developer documentation for the Campaign Management API v5 states that it will be sunset on January 26, 2027, and points developers to the Apple Ads Platform API, which supersedes it.

According to Apple's documentation and coverage from 9to5Mac, the Platform API is the single API for Apple Ads going forward, and it adds things v5 never had, including:

• Search popularity data for keywords.
• Change history for campaigns.
• Reporting by ad position.
• Support for ad placements beyond the App Store, such as Apple Maps.

Check Apple's documentation for the exact endpoints and dates before you plan; secondary reports have disagreed on some details, such as when the new API first became available.

Who this affects

• Developers with their own scripts that create campaigns, change bids, add negative keywords or pull reports.
• Teams using third party tools for Apple Ads. Ask each vendor when they move to the Platform API. If they cannot answer, treat that as a risk.
• Anyone with a dashboard that pulls Apple Ads spend or installs through the API. Reports break the same day writes do.

If you only manage Apple Ads by hand in the web console, nothing changes for you.

A migration checklist

1. Find every caller. Search your code and servers for the v5 base URL and list every script, cron job and integration that uses it. Include anything a contractor set up.
2. Ask your vendors. Get a date from each tool you pay for.
3. Move reads first. Reporting is the safest place to start: compare a week of spend, taps and installs from both APIs side by side. The numbers should match before you trust the new one.
4. Then move writes, one type at a time: bids, then keywords, then campaign settings. Keep every write in dry run mode until the reads match.
5. Cut over before January 26. Aim for the week of January 11 to leave room for surprises, and do not schedule a big campaign change for the last week.
6. Delete the old code once the new path has run cleanly for a week, so nothing quietly falls back to v5.

What to watch after the switch

• Spend and installs should match what the console shows. A gap usually means a missing campaign or a time zone difference in reports.
• Rate limits. New APIs come with their own limits; space out bulk calls and handle a refusal by waiting and retrying, not by hammering.
• Errors in silent jobs. A nightly report that fails without alerting anyone is the most common way migrations go wrong.

How this fits with organic ranks

Apple Ads and organic search work together: ads can lift an app's downloads, and downloads feed into how apps rank. Altitude tracks your organic App Store ranks and competitors today; you can add your app for free or see pricing. If you are measuring an ad campaign, compare your organic ranks for the same keywords before and after, using weekly averages rather than single days, as covered in why your App Store rank moves every day.

Questions

Will my campaigns stop running on January 26?

The shutdown is of the API, not of Apple Ads. Campaigns keep running; what stops is any automation or reporting that still calls v5.

Do I need a new API key?

Check Apple's Platform API documentation for its access setup before you start, and test your credentials early in your migration.

Is the web console changing?

The announcement covers the API. Campaigns you manage by hand in the Apple Ads console are not affected by the API shutdown.