Apple in-app purchase metadata API changes: what changes and what does not
Apple is retiring older endpoints for editing in-app purchase and subscription metadata. For apps using a subscription platform for product editing, the key question is whether selling and delivering access are affected. They are not: the change concerns how product metadata is created and edited in App Store Connect, not purchase processing or entitlement delivery.
What Apple is changing
Apple has warned that deprecated endpoints for in-app purchase and subscription metadata will start to be removed in early 2027. The affected area is metadata editing: names, localizations and images attached to products. If you received that warning and use a subscription platform to edit products, the practical effect is narrower than it may first appear. No SDK update and no configuration change are required because of this change. Purchase processing, renewals, restores, entitlements, webhooks and product sync are unaffected.
From direct edits to version-based metadata
Under the older approach, localizations and images sat directly on an in-app purchase, subscription or subscription group, and you edited them in place. App Store Connect API 4.4.1 introduces a version-based approach instead. In that model, each version acts as the review-bound package for a product's descriptive assets, so text and artwork are grouped under the version rather than the product itself. Starting a fresh version for each round of edits isolates pending changes from what shoppers currently see. Existing integrations can still use the deprecated endpoints during the transition while they move to the replacement workflow.
What this means for customers
The change touches only the tools that create or edit product metadata in App Store Connect: Product Editor and the product tools available through the MCP server. It does not touch the services your app relies on to sell subscriptions and grant access. Use the checklist below to separate the two groups quickly. If your concern is checkout, renewal, restore, entitlement delivery, webhook delivery or importing products, none of those paths use the affected endpoints.
Migration status and what to expect
Product Editor and the MCP product tools are being moved to the version-based endpoints, with completion planned before Apple's removal date and a target of December 2026. Until then, those features continue to work on the current endpoints, which Apple still supports. The new flow adds steps on Apple's side: a product needs a draft version, localizations attach to that version, and the version is submitted for review. That extra handling is done for you, so you continue to use Product Editor in the same way.
| Area | Affected? | What to do |
|---|---|---|
| Product Editor and MCP product tools | Yes — being migrated | No action; keep using the tools as before |
| Purchase processing and receipt validation | No | No action |
| Renewals and restores | No | No action |
| Entitlements | No | No action |
| Webhooks and integrations | No | No action |
| Product import and sync from App Store Connect | No | No action |
| SDK version or platform configuration | No minimum version | No update or configuration change required |
Based on the affected endpoints described for product metadata editing; purchase and access-delivery paths do not use those endpoints.
Frequently asked questions
Has the move away from the affected endpoints finished?
No. The work is in progress and limited to product-editing tools. The affected endpoints have not yet been fully replaced.
When is the move expected to finish?
Completion is planned before Apple removes the deprecated endpoints, with a target of December 2026. Until then, the current endpoints remain supported.
Do I need to update the SDK or change configuration?
No. There is no minimum SDK version for this change and no configuration change is required, because it affects only how the platform communicates with App Store Connect.
Are purchases, renewals, restores, entitlements, webhooks or product sync affected?
No. Purchases, renewals, restores, entitlements, webhooks and product sync do not use the affected endpoints.
Where can I find updates?
This page will be updated once the migration is complete.