Apple Ads APIs: Platform API shipped; Campaign Management API 5 still callable until 2027
Engineers should plan against the live Platform API and API 5 changelogs—not a blog feature list—and the 26 January 2027 Campaign Management sunset.
Apple’s developer documentation now states that the Apple Ads Platform API supersedes the Apple Ads Campaign Management API, which will be sunset on 26 January 2027. The Platform API is documented as a single RESTful interface for App Store and Apple Maps campaigns. Campaign Management API 5 remains documented and continues to receive versioned changes, so teams can still call it today—they should not treat “superseded” as “already offline”. Apple Ads; Platform API.
Endpoint scorecard (documented, not account-tested)
| Surface | Status in docs (checked 19 Sep 2026) | What a team can plan against |
|---|---|---|
| Apple Ads Platform API | Live documentation for Org/Me, Ad Accounts, Campaigns, Ad Groups, creatives/assets, App Store reports, Brands/Maps reports, insights, recommendations | App Store **and** Apple Maps campaign management through one REST interface |
| Campaign Management API 5 | Still documented; calling guide still shows `https://api.searchads.apple.com/api/v5/...` | Existing Search Ads integrations can keep calling v5 until the sunset date |
| Campaign Management API 5.5 (Feb 2026) | Maximize Conversions automated bid strategy; automated ad groups with Search Match | Bid-strategy payload changes on Create/Update Campaign and reporting endpoints |
| Campaign Management API 5.6 (Jun 2026) | Lifetime budgets / `budgetAmount` removed; use `dailyBudgetAmount` | Any script still sending lifetime budget fields needs a fix |
| Creative Sets (API 5) | Deprecated and unavailable in API 5 | Do not plan new Creative Sets work against API 5 |
| Campaign Management API sunset | **26 January 2027** per Apple Ads overview | Migration deadline for production callers |
Sources: Platform API overview; API 5 changelog; Apple Ads overview sunset note.
Separate shipped docs from unverified account access
This check reads Apple’s public documentation. It does not execute authenticated calls, certify org entitlements for Maps brands, or verify third-party bidding vendors’ migration status. “Documented endpoint” is not the same as “this org’s token returned 200 today”.
Practical implication
Stop designing new multi-surface automation solely against Campaign Management API 5 feature folklore. Use the Platform API reference for App Store + Maps work, keep API 5 callers on a dated migration plan ending 26 January 2027, and treat 5.6’s removal of lifetime budgets as a breaking change for any remaining v5 writers.
Inspect the evidence
Download the endpoint scorecard timeline. The extraction separates documented facts from our analysis and unknowns.
| Field | Evidence or limit |
|---|---|
| Earlier record | 2026-08 — Archive checklist covered the unified Platform API announcement and open questions on analytics depth and legacy deprecation timing. |
| Later evidence | Apple Ads docs: Platform API supersedes Campaign Management API; sunset **26 January 2027**; API 5.5/5.6 changes documented. |
| Outcome supported | Platform API is the documented successor and is publicly specified; API 5 remains callable in docs until the stated sunset |
| Still unconfirmed | Authenticated call success per org; vendor adapter readiness; completeness of Maps analytics versus App Store reporting |
| Next check | Diff production clients against Platform API paths; schedule API 5 retirement before 2027-01-26 |
Further reading in the existing archive: Apple's unified campaign management API: a checklist. That link provides background; this check does not independently verify its full contents.
