Apple Ads Platform API Migration: Why This Is a Marketing Deadline, Not Just an Engineering One

Katie Melvin

Sep 28

6 min read

Apple is retiring the original Apple Ads Campaign Management API on January 26, 2027, replacing it with a new, unified Apple Ads Platform API that manages both App Store and Apple Maps advertising through a single interface. Any Apple Search Ads workflow that still runs on the old API — a homegrown script, an agency's internal dashboard, or a third-party platform — loses the ability to manage campaigns and pull reporting data after that date. If you run paid App Store campaigns, this belongs on a marketing leader's calendar now, not buried in an engineering backlog you'll get to eventually.

What is the Apple Ads Platform API, and why is Apple replacing the old one?

Apple released version 1.0 of the Apple Ads Platform API in August 2026, consolidating what used to be separate integrations for App Store search ads and the newer Apple Maps ad placements (which went live around mid-August 2026) into one REST-based interface. Instead of maintaining two sets of credentials and endpoints, advertisers and their tools now authenticate once and manage campaigns, keywords, creative assets, reporting, and change history across both surfaces from the same API.

The old Apple Ads Campaign Management API (version 5) was purpose-built for App Store search ads only, before Apple Maps advertising existed as a product. As Apple's ad surfaces multiplied, a single unified API became the more sustainable path — which is also why the migration deadline isn't optional or quietly extendable the way some API sunsets end up being. Apple has stated a firm date: campaigns and reporting on the old API stop working on January 26, 2027.

What's actually different between the old API and the new one?

The functional scope is similar — campaign creation, keyword management, reporting — but the mechanics changed in ways that matter for anyone building or buying automation on top of it.

	Apple Ads Campaign Management API (v5)	Apple Ads Platform API (v1.0)
Ad surfaces covered	App Store search ads only	App Store + Apple Maps ads
Retirement status	Retires January 26, 2027	Current, actively developed
Rate limiting	Undocumented/inconsistent	Standardized RateLimit-* headers based on draft IETF specs
Authentication	Separate flows per surface	Unified credentials
Scope	Campaigns, keywords, reporting	Adds asset handling and change-history tracking

The rate-limiting change is worth calling out specifically: the new API returns explicit RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers with documented backoff behavior. For any tool pulling reporting data on a schedule — which is most of them — that's a meaningfully more predictable system to build against than guessing at undocumented throttling, which has historically been a real pain point for Apple Search Ads reporting integrations.

What happens if my tools don't migrate by January 26, 2027?

Campaign management and reporting through the old Campaign Management API stop functioning after that date. In practice, that means you could lose the ability to adjust bids, pause campaigns, or pull performance data — not because your budget or your app changed, but because the pipe your tool used to talk to Apple got shut off.

This is the kind of failure that's easy to miss until it's urgent, for one specific reason: it's not something that shows up as a line item on a roadmap you're tracking. It shows up as a support ticket, a dashboard that stops updating, or a campaign that silently stops spending — and by the time someone notices, you've lost days of visibility or performance during whatever window it takes to get fixed.

Do I need to do anything if I use MobileAction, SplitMetrics, AppTweak, or Newton?

You need to ask, even if you don't need to build anything yourself. If your Apple Search Ads program runs through a third-party ASO or ad-intelligence platform rather than a direct API integration, the migration work is technically theirs to do — but you're the one who inherits the consequences if it doesn't happen on time.

The players in this space approach Apple Search Ads management differently, which is useful context for knowing what questions to ask each:

MobileAction — an ASO and ad-intelligence platform with keyword tracking, competitor intelligence, and Apple Search Ads campaign management built on top of Apple's official API.
SplitMetrics (via its SplitMetrics Acquire product) — focused on Apple Search Ads campaign optimization and creative testing for App Store product pages, also built on Apple's ad APIs.
AppTweak — an ASO platform that pairs keyword and metadata optimization with Apple Search Ads management and reporting.
Newton (by Affle), an official Apple Ads Partner — positions itself around automated, "autopilot"-style Apple Search Ads bid management, which makes it especially dependent on reliable, low-latency API access.

None of these vendors have publicly detailed their individual migration timelines as of this writing, which is exactly the point: this isn't information you should assume, it's a two-minute question to put in front of your account manager or support contact. Ask directly whether your platform has migrated to the Apple Ads Platform API, and if not, what their timeline is relative to the January 26, 2027 cutoff.

Worth noting: this isn't a "pick one tool" situation. Brightlake isn't positioned to replace MobileAction, SplitMetrics, AppTweak, or Newton — we work alongside whatever MMP (mobile measurement partner) or ASO stack a team already has in place. The migration question above is about your existing tooling staying functional; it's not an argument for switching platforms.

How should marketers audit their Apple Search Ads stack right now ahead of the Apple Ads API Migration?

This doesn't require an engineering sprint. It requires an inventory and a few pointed questions, ideally done well before Q4 budget planning collides with the holiday shopping season:

List every tool, script, or agency workflow touching your Apple Search Ads account. Include anything pulling reporting data, not just bid-management tools — attribution and BI pipelines count too.
Ask each vendor, in writing, whether they've migrated to the Apple Ads Platform API. A vague "we're aware of it" is not a confirmed migration.
If you or your team built anything on the old API directly (a reporting script, a custom bid automation tool), flag it for your engineering team now — a five-month-plus runway is generous, but only if someone starts the clock.
Build in a buffer before the deadline, not up against it. Migrations that touch billing-adjacent systems tend to surface edge cases late.
Confirm your reporting continuity plan — if a tool's migration slips, do you have a fallback way to monitor spend and performance during the gap?

Is this connected to Apple's other 2026 Apple Ads changes?

Loosely, in that it's part of the same broader modernization push — Apple also rolled out Maximize Conversions automated bidding and additional App Store search ad placements earlier in 2026 — but the API migration is a separate, infrastructure-level change. You can be fully caught up on bidding strategy and placement changes and still be exposed here, because this isn't a campaign-settings problem. It's a plumbing problem, and plumbing problems don't announce themselves until they fail.

The takeaway

The Apple Ads Platform API migration is a compliance-style deadline wearing an engineering costume: January 26, 2027 is a hard cutoff, it affects anyone running Apple Search Ads or Apple Maps ad campaigns through automated tooling, and the actual work of confirming readiness takes an afternoon of vendor emails, not a development cycle. Treat it as a vendor-risk audit owned by whoever owns the Apple Search Ads budget, not a ticket that waits for engineering bandwidth.

FAQ

Q: What is the deadline for the Apple Ads Platform API migration?A: January 26, 2027. After that date, the original Apple Ads Campaign Management API (v5) no longer supports campaign management or reporting calls.

Q: Does this affect Apple Search Ads bidding features like Maximize Conversions?A: Not directly — Maximize Conversions is a bidding strategy inside your campaigns, separate from which API moves the underlying data. But if the automation running that bidding strategy is built on the old API, that automation breaks unless it's migrated before the deadline.

Q: I use a third-party tool like MobileAction, SplitMetrics, AppTweak, or Newton for Apple Search Ads — do I need to do anything?A: You don't need to build the migration yourself, but you do need to confirm your vendor has completed or scheduled theirs. Ask directly rather than assuming it's handled.

Q: Will my Apple Search Ads campaigns just stop running if the API isn't migrated in time?A: Active campaigns aren't automatically paused, but you lose the ability to manage bids, adjust budgets, and pull reporting through the old API — which in practice means losing control and visibility, even if spend continues unmanaged in the background.

Q: Where does Brightlake fit in if I already use MobileAction, SplitMetrics, AppTweak, or Newton?A: Alongside them, not instead of them. Brightlake is built to work with the MMP you already have rather than ask you to migrate off it, so this API deadline doesn't change what tool you should be using — it's about confirming your current one (whichever it is) is ready for January 26, 2027.

Sources: