Apple has released version 1.0 of the Apple Ads Platform API, a single REST interface that lets developers and agencies build and manage advertising campaigns across both the App Store and Apple Maps through one set of endpoints, according to Apple's developer documentation. The release, dated August 2026 in Apple's own changelog, also sets a firm retirement date for the API it replaces: the existing Apple Ads Campaign Management API will stop working on January 26, 2027.

The new interface consolidates what had been two separate advertising surfaces requiring two different integration paths. Apple's documentation describes the Apple Ads Platform API as a way to "programmatically manage App Store and Apple Maps advertising campaigns through a single RESTful API." Before this release, App Store advertising ran on the Campaign Management API, now in its fifth major version, while the newer Apple Maps advertising product - which went live for advertisers in the United States and Canada earlier in 2026 - had no equivalent programmatic layer of its own.

That gap is now closed. According to Apple's documentation, the Platform API covers account management, app and brand search, campaign and ad group creation, keyword and negative keyword management, creative and asset handling, product pages, bulk operations, budget orders, reporting, insights, recommendations, suggestions and a dedicated change-history endpoint set. The overview page frames the scope in practical terms: developers "can build campaigns with budgets, and create ad groups that include keywords, audience refinement criteria, and scheduling," and, through the same interface, "create and manage ads and creative assets, configure targeting and bidding, and monitor performance through reports, insights, and recommendations," according to Apple.

A hard deadline for the old API

The most consequential detail for agencies and in-house teams running programmatic Apple Ads accounts is not the new API itself but the clock now running on the old one. Apple's documentation states plainly that "the Apple Ads Platform API supersedes the Apple Ads Campaign Management API, which will be sunset on January 26, 2027." That is a Tuesday, roughly five months from the Platform API's own release.

The Campaign Management API has not stood still while the successor was being built. Apple's changelog for that API shows a version released as recently as June 2026, when lifetime budgets were deprecated and the budgetAmount field was removed from both the API and its documentation, leaving dailyBudgetAmount as the only supported way to set a campaign's spending ceiling. Two months earlier, in February 2026, the same API introduced Maximize Conversions, an automated bid strategy that targets a cost-per-acquisition figure the advertiser sets, working through an automated ad group paired with Search Match to discover and bid on relevant keywords without manual keyword entry. That shift away from manual bid caps was one of the larger changes to Apple's advertising mechanics in 2026, and it now sits inside an API with a fixed end date.

For any team still integrated against Campaign Management API version 5, the sunset date functions as a migration deadline rather than a suggestion. Apple's own guidance elsewhere in its developer materials, cited in third-party client libraries that track the same changelog, describes the consequence directly: after the sunset date, calls against the old API return errors, and campaigns can no longer be managed, edited, or reported on through that interface.

What version 1.0 actually contains

Apple's changelog entry for the Platform API is short, reflecting the fact that this is a first release rather than an iteration. It records a single line: "Initial release of the Apple Ads Platform API, including Advertising Your App on the App Store and Advertising Your Business on Apple Maps," according to Apple. Those two linked guides function as onboarding tracks, walking a new integrator through launching a first campaign on each placement rather than documenting the full endpoint set in prose.

The fuller picture comes from the API's topic index, which groups roughly eighteen functional areas under headings that map closely onto how a campaign actually gets built and run. Account management endpoints handle authentication scope and role-based access. A Search Apps and App Eligibility cluster lets a caller check whether a given app qualifies to run App Store ads before committing budget, and look up rejection reasons for creatives that fail review. A separate cluster, grouped under "Ads on Apple Maps," covers brand and business-category lookups, location groups, and the metric types specific to Maps campaigns - reflecting that geographic advertising carries different targeting primitives than search-result advertising does.

Campaigns, ad groups, geo targeting, keywords and negative keywords, ads, creatives, and assets each get their own endpoint and data-object documentation, following a pattern already familiar to anyone who has integrated against the Campaign Management API. Reporting is split into App Store Reports and Brands Reports endpoints, a division that persists the underlying distinction between the two ad surfaces even though both now sit behind one authentication layer and one base API. Insights, recommendations and suggestions round out the set: insights cover impression share and search-term popularity; recommendations and suggestions surface budget, Target CPA, keyword, phrase and category guidance that a caller can query, apply or dismiss programmatically.

A change history endpoint group, present from this first version, lets a caller retrieve audit summaries and detailed change records for entities inside an ad account - useful for agencies managing accounts on behalf of clients who want a record of what was modified, when, and by which credential.

Rate limits arrive with explicit headers

Apple published a companion article, "Applying Rate Limits," alongside the Platform API launch, and it is the most technically detailed piece of the release for engineering teams building or maintaining an integration. According to Apple's documentation, "rate limits exist in the Apple Ads Platform API to avoid latency and other system problems from too many API calls within a limited time," and every response the API returns, whether the call succeeded or failed, carries a set of rate-limit headers based on a draft IETF specification for standardized rate-limit fields.

Three headers do the work. RateLimit-Limit reports the total request quota allotted to the caller for the current window. RateLimit-Remaining reports how many of those requests are left. RateLimit-Reset reports the number of seconds until the window resets and the remaining count returns to the full limit - expressed, notably, as a countdown in seconds rather than a fixed timestamp, which Apple's documentation says keeps it consistent with the separate Retry-After header used specifically on rejected requests.

That distinction between the two headers matters operationally. When the server rejects a call with a 429 status and a rate_limit_exceeded error, the response adds a Retry-After header giving the exact number of seconds to wait before the next request will be accepted. Apple's guidance is explicit that developers should prefer Retry-After over RateLimit-Reset when both are present on a 429 response, "because it reflects the exact wait for that rejected request," according to the documentation.

For teams building against the raw HTTP interface rather than a generated SDK, Apple lays out a specific pacing algorithm rather than leaving the strategy to interpretation. The guidance recommends checking RateLimit-Remaining before issuing the next request and, if it is running low, waiting roughly the number of seconds RateLimit-Reset specifies rather than continuing until a 429 arrives. If a request does fail with 429, the documentation calls for waiting the number of seconds Retry-After specifies, falling back to RateLimit-Reset and then to a default if neither header is present. It further recommends doubling the wait on each consecutive 429 up to a stated ceiling of 16 seconds, holding at that maximum rather than continuing to increase it, and resetting the backoff counter to its minimum once a request finally succeeds.

Apple's own example code, included in the documentation, implements exactly that pattern: an exponential backoff function starting at a two-second wait, doubling on each retry up to the 16-second ceiling, and reading the three rate-limit headers off every response to decide whether to slow down proactively. The same header-reading logic applies to Apple's generated client libraries. Rather than exposing raw HTTP responses, methods in the generated SDKs offer a _with_http_info counterpart that returns a data, status code and headers tuple, letting a caller read RateLimit-Remaining and RateLimit-Reset from that tuple using the identical logic, according to Apple's documentation.

Apple states the header-aware backoff approach applies "to every endpoint that returns a 429, regardless of which HTTP client or SDK you use." No specific numeric quota - the actual value of RateLimit-Limit a typical account receives - appears in the published documentation reviewed for this article; Apple's example response shows a limit of 100 requests per window with 4 remaining and a 37-second reset, but the company does not state whether that figure is illustrative or represents an actual default tier.

The context: two ad surfaces, one API

The timing of a unified API is not incidental. Apple Maps began carrying advertising for businesses in the United States and Canada earlier in 2026, arriving through Apple Business, a consolidated platform that replaced three earlier separate products - Business Connect, Business Manager and Business Essentials - on April 14, 2026 across more than 200 countries and regions. Apple's chief financial officer, Kevan Parekh, had confirmed the Maps advertising plan on an April 30, 2026 earnings call, describing ads that would appear "during key search and discovery moments" in the United States and Canada that summer.

When Maps ad buying opened to advertisers, Apple's own overview materials already pointed toward a fuller programmatic layer, promoting the Apple Ads Platform API by name as the tool to "build, manage, and scale local campaigns with ease," according to Apple, even before that API had shipped. At the time, it remained an open question whether Maps campaigns would be governed by the same interface as App Store campaigns or a separate one. Version 1.0 answers that question: both placements now sit behind the same base API, authentication layer, and rate-limit system, even though reporting, targeting objects and creative types remain split into App Store-specific and Maps-specific (Brands) endpoint groups underneath that shared surface.

App Store advertising itself has been in active flux through 2026, which is part of why a unified, better-documented API mattered to the developer and agency community integrating against it. Apple made Maximize Conversions generally available to all App Store search-results advertisers on February 26, 2026, retiring the CPA-cap bidding approach that had governed the format since it launched in October 2016. The following month, Apple began rolling out multiple ad positions inside App Store search results, starting in the United Kingdom and Japan on March 3, 2026, the first increase in search-result ad density since the App Store advertising product first launched.

That bidding and placement activity was already running through the existing Campaign Management API. An independent auction analysis published in March 2026 by the agency ConsultMyApp, drawing on 132 keywords and 627 auction observations from the UK App Store, found that bid strength outweighed relevance in roughly 44 percent of observed cases - a finding that underscored how much weight programmatic bid management, exactly the kind of activity the Campaign Management API and now the Platform API exist to automate, carries in determining which app wins the top search position.

What changes for agencies and developers

For a large agency or a developer with an existing Campaign Management API integration, the practical task ahead is migration rather than adoption from scratch. Apple's documentation does not describe an automatic transition; existing integrations built against version 5 of the Campaign Management API will need to be rebuilt against the new Platform API's endpoint set before January 26, 2027, or lose the ability to manage and report on live campaigns through code.

The consolidation carries a secondary implication for holding companies and multi-location retailers running both App Store and Apple Maps advertising simultaneously. Rather than maintaining two separate authentication flows, two sets of client credentials, and two integration codebases, a single OAuth-based connection to the Platform API can now, in principle, reach both advertising surfaces. Whether Maps campaigns inherit the same automated bidding architecture that App Store search campaigns gained through Maximize Conversions is not addressed in the documentation reviewed for this article and remains undocumented by Apple as of this release.

The rate-limit specification also gives integrators a firmer basis for capacity planning than existed previously. A documented, header-driven backoff protocol, with Apple's own reference implementation published alongside it, removes much of the guesswork that previously accompanied building resilient polling and reporting jobs against Apple's advertising infrastructure - work that agencies managing dozens or hundreds of client accounts perform continuously to keep budget pacing, keyword bidding and performance dashboards current.

Why this matters for the marketing community

The release lands inside a broader pattern PPC Land has tracked across 2026: platform advertising APIs increasingly publish explicit, machine-readable rate-limit contracts rather than leaving pacing to trial and error. Google added rate-limit and cost dashboards to its Gemini API in March 2026 after billing incidents tied to unclear usage visibility, while Meta has been pushing developers away from polling toward webhook-based updates specifically because polling "chips away at rate limits," according to Meta. Apple's approach - standardized headers based on a draft IETF specification, paired with a published reference backoff algorithm - fits that same industry direction toward giving API consumers explicit signals rather than opaque throttling.

The unification of App Store and Apple Maps under one API also matters because it formalizes something Apple had been building toward gradually rather than announcing as a single strategic move. The company rebranded its advertising business from "Apple Search Ads" to "Apple Ads" in April 2025, a name change PPC Land covered at the time as a signal that the business intended to expand beyond App Store search placements. Apple Maps advertising, the Apple Business platform consolidation, and now a single Platform API replacing a search-specific Campaign Management API each represent a further step in that same direction. For marketers and agencies, the practical consequence is that Apple's advertising surface area is no longer confined to app discovery; it now spans local business discovery as well, unified under infrastructure that a single integration can reach.

The five-month runway to the Campaign Management API's retirement is comparatively short by the standards of major advertising platform migrations, and it places a concrete deadline on engineering roadmaps at agencies that had, until this release, no fixed date to plan against.

Timeline

  • October 2016 - App Store search advertising begins, introducing the CPA-cap bidding mechanism that would remain in place for nearly a decade.
  • April 2025 - Apple rebrands its advertising business from Apple Search Ads to Apple Ads, signaling plans to expand beyond App Store search.
  • May 2025 - The Campaign Management API's Create a Campaign endpoint gains support for an optional total-budget budgetAmount field, according to Apple's changelog.
  • December 2025 - Apple documents plans for multiple ad positions inside App Store search results, arriving in 2026.
  • February 26, 2026 - Apple makes Maximize Conversions generally available to all App Store advertisers, retiring the CPA-cap bidding approach.
  • March 3, 2026 - Apple begins rolling out multiple ad positions in App Store search results, starting in the United Kingdom and Japan.
  • March 2026 - Independent analysis by ConsultMyApp finds bid strength outweighs relevance in roughly 44 percent of observed App Store auction cases.
  • March 24, 2026 - Apple announces the Apple Business platform, bundling Apple Maps advertising with device management and communication tools.
  • April 14, 2026 - Apple Business becomes available across more than 200 countries and regions, replacing Business Connect, Business Manager and Business Essentials.
  • April 30, 2026 - Apple's chief financial officer confirms Apple Maps advertising for the United States and Canada on a fiscal second-quarter earnings call.
  • June 2026 - The Campaign Management API deprecates lifetime budgets, removing the budgetAmount field in favor of dailyBudgetAmount, according to Apple's changelog.
  • Earlier in 2026 - Apple Maps ad buying opens to advertisers in the United States and Canada, with the still-unreleased Apple Ads Platform API already promoted in Apple's overview materials.
  • August 2026 - Apple releases version 1.0 of the Apple Ads Platform API, unifying App Store and Apple Maps campaign management, according to Apple's documentation.
  • January 26, 2027 - The Apple Ads Campaign Management API is scheduled to be sunset, according to Apple's documentation.

Summary

Who: Apple, through its Apple Ads advertising division, and the developers and agencies that build programmatic integrations against Apple's advertising APIs.

What: Apple released version 1.0 of the Apple Ads Platform API, a single RESTful interface unifying App Store and Apple Maps campaign management, and set January 26, 2027 as the retirement date for the Apple Ads Campaign Management API it replaces. The new API ships with a documented, header-based rate-limiting system built on a draft IETF specification.

When: Apple's documentation dates the Platform API's initial release to August 2026. The Campaign Management API sunset takes effect January 26, 2027.

Where: The change applies to Apple's global developer-facing advertising infrastructure, covering App Store campaigns across the storefronts Apple Ads serves and Apple Maps campaigns currently available in the United States and Canada.

Why: Apple had been expanding its advertising business across two increasingly distinct surfaces, App Store search and Apple Maps local discovery, using different programmatic interfaces for each. The Platform API consolidates that infrastructure into one integration point ahead of a hard deadline that forces existing Campaign Management API integrations to migrate.