Apple Ads Platform API (v1.0): one API for App Store + Apple Maps, and the Campaign Management API sunsets Jan 26, 2027

Apple quietly shipped Apple Ads Platform API v1.0, a unified REST API that covers both App Store ads and Apple Maps ads, and it comes with a hard stop: the legacy Apple Ads Campaign Management API sunsets on Jan 26, 2027.

• Source: PPC Land, “Apple Ads Platform API debuts as old API faces 2027 shutdown” (published Sep 3, 2026)
• Read: https://ppc.land/apple-ads-platform-api-debuts-as-old-api-faces-2027-shutdown/
• Primary docs: Apple Ads Platform API overview
  • https://developer.apple.com/documentation/apple-ads-platform-api

What changed (the practical version)

1) One API surface for two ad products

If you run Apple Ads at any scale and you (or your agency) manage campaigns programmatically, the big structural shift is one integration path for:

• App Store ads (what most teams mean by “Apple Ads”)
• Apple Maps ads (the newer placement)

That matters because workflows, tooling, and reporting pipelines tend to ossify around “one product, one API”. This removes that excuse.

2) The sunset date is the real deadline

Apple’s docs explicitly position the Platform API as the successor, with a sunset date for Campaign Management API:

• Campaign Management API stops working: Jan 26, 2027

For teams still on v5 of Campaign Management API, this turns into a real migration plan, not a “nice to have”.

3) Rate limiting becomes an operational design constraint

Apple is being unusually explicit about rate-limit headers and recommended backoff behaviour (429 handling, Retry-After precedence, exponential backoff).

This is the kind of detail that only becomes interesting when it breaks your automation at the worst possible moment (seasonality, a major release, a budget shift).

What to do with this (if you are responsible for performance + delivery)

• Treat this like a platform migration, not a marketing item. Put a date on it, assign an owner, and inventory every place you touch the API (bid tools, reporting, scripts, dashboards, QA tooling).
• Assume your reporting shape will change. Even if “it’s the same metrics”, unified platforms tend to introduce new entity types and edge cases.
• Make rate limiting visible. If you do not already log 429s and headers, you are flying blind.

Tiny win (45 minutes)

Write a one-page “Apple Ads API dependency map”:

1. Which systems call the Campaign Management API today?
2. What breaks if they stop (campaign creation, bid updates, reporting, QA checks)?
3. Who owns the migration, and what is the earliest internal deadline you can live with?

Read the source: https://ppc.land/apple-ads-platform-api-debuts-as-old-api-faces-2027-shutdown/