New REST API: Manage Products, Offerings and Entitlements Server-Side
A rebuilt REST API was designed around developer workflows rather than the needs of mobile SDKs. Its first endpoints focus on product setup, with clearer listing, error handling and permission controls.
Why rebuild the API
The earlier API was shaped around endpoints used by SDKs, which made sense for in-app calls but was less natural for server-side administration. The rebuilt version starts from the tasks developers perform when extending an application: discovering records, handling failures clearly, respecting rate limits, and restricting credentials.
The first batch lets you create, retrieve and manage products, offerings and entitlements. Additional endpoints were intended to follow during the year, so treat this as the starting scope rather than a complete platform surface.
Developer controls to check first
Use this checklist when deciding whether the API fits a setup task:
- Confirm the task is product, offering or entitlement management rather than a customer lookup.
- Check whether listing and pagination cover the number of records you need to scan.
- Plan for explicit error responses and rate-limit headers in retries and monitoring.
- Create separate API keys per domain and accessibility level instead of sharing a broad key.
- Decide which store products should be synced, and which entitlements, offerings and packages they belong to.
- Test updates for a small catalogue before applying the workflow to thousands of products.
Fine-grained permissions are central to this design: a key for reading products does not need permission to change offerings, and a setup tool does not need unrelated access.
Automating product setup
Product setup is the clearest use case. Instead of entering every item manually in a dashboard, you can create platform products programmatically and connect them to entitlements, offerings and packages. The same server-side workflow can add, change or list records whether the catalogue is small or very large.
Practical examples include syncing newly released store items, handling games with consumables and non-consumables, adding creator subscriptions frequently, displaying web products on a website, and running an internal dashboard that collects product creation in one place before syncing it through.
Examples: terminal and Fastlane workflows
Two early examples show how teams used the endpoints outside a browser. One terminal tool created products, offerings and entitlements from the command line, replacing manual dashboard steps and helping script setup. Another Fastlane plugin compared App Store Connect products with platform products, highlighted missing items, and imported them with a single action.
These were internal experiments rather than officially supported products, so evaluate maintenance, credentials handling and error behaviour before adopting either pattern.
What was still being worked on
Two directions were still in development. A more consistent data model aimed to hide differences between app stores behind shared concepts. A more RESTful design also aimed to make GET operations safe to repeat: reading customer details should not create a new app user ID or otherwise change the record.
That distinction matters for support and analytics tools. A read-only lookup should return subscription and purchase-lifecycle information without side effects, while any creation or mutation should be an explicit, intentional operation.
Beta and next steps
Early access was offered to developers who wanted to try the API before launch and provide feedback. If you are evaluating this design today, check the current documentation and availability first, then map your product-setup task against the endpoints and permission model described above.
| Workflow | What it does | Best fit |
|---|---|---|
| Terminal tool | Creates products, offerings and entitlements from the command line | Repeatable setup and scripting |
| Fastlane plugin | Finds App Store products missing from the platform and imports them | Store catalogue reconciliation |
| Internal dashboard | Centralises product creation and syncs it through the API | Large or frequently changing catalogues |
Examples described at launch; support status was not official.
Frequently asked questions
What did the first release cover, and what was still planned?
The first batch covered creating, retrieving and managing products, offerings and entitlements. Broader endpoints were planned for later release, including a more consistent data model across app stores and read operations for customer information without side effects.
Can access be restricted by API key?
Yes. API keys could be limited to specific domains and accessibility levels, so each key only needs the access its task requires.
What product-setup tasks can be automated?
Sync store products into the platform, attach them to entitlements, offerings and packages, list or update them server-side, show web products on a website, or build an internal dashboard that adds products in one place.