Apple recently emailed developers about changes to the App Store Connect API, warning that deprecated In-App Purchase and subscription endpoints will begin to be removed in early 2027. If you received that email and use RevenueCat, here’s what it means for your app.

First of all, you don’t need to update your RevenueCat SDK or change your configuration because of Apple’s In-App Purchase metadata API changes. Your purchases, renewals, restores, entitlements, webhooks, and product sync are unaffected.

RevenueCat uses the affected App Store Connect endpoints in our product editing tools, but we’re migrating those tools to Apple’s replacements and will complete the migration before Apple removes the deprecated endpoints.

What Apple is changing

App Store Connect API 4.4.1 introduced a version-based workflow for In-App Purchase, subscription, and subscription group metadata. Previously, localizations and images were attached directly to an In-App Purchase, subscription, or subscription group. To change them, you updated the metadata on that product.

With the new workflow, localizations and images belong to a version: a container for metadata that goes through App Review. You create a new version when making changes, keeping the proposed updates separate from the metadata already live on the App Store.

Existing integrations can still use the deprecated endpoints during the transition. Apple’s migration guide explains the replacement workflow.

What this means for RevenueCat customers

These changes affect how RevenueCat creates or edits product metadata in App Store Connect through Product Editor and the product tools available through our MCP server.

They don’t affect the services your app uses to sell subscriptions and deliver access:

  • Purchase processing and receipt validation
  • Renewals and restores
  • Entitlements
  • Webhooks and integrations
  • Product import and sync from App Store Connect

There’s no minimum RevenueCat SDK version for this migration, and you don’t need to change your RevenueCat configuration.

Migration status

We're migrating Product Editor and the MCP product tools to the version-based endpoints. We'll complete the migration before Apple's removal date, and we're targeting December 2026. Until then, these features keep working on the current endpoints, which Apple still supports.

The new flow has more steps on Apple's side. Products need a draft version, localizations are attached to that version, and the version goes through a review submission. RevenueCat will handle all of that for you. You'll keep using Product Editor the same way.

FAQ

Has RevenueCat migrated off the affected endpoints?

Not yet. We use them only in Product Editor and the MCP product tools, and the migration is in progress.

When will the migration be done?

Before Apple's removal date. We're targeting December 2026

Do I need to update the SDK or change any configuration?

No. This change only affects how RevenueCat talks to App Store Connect, and there's no minimum SDK version tied to it.

Are purchases, renewals, restores, entitlements, webhooks or product sync affected?

No. None of these use the affected endpoints.

Where can I find updates?

We'll update this page when the migration is complete.