App Store Connect
Connect your Apple products, purchases, and subscription notifications.
The App Store Connect integration gives Nuxie access to your Apple catalog and subscription state. Server notifications keep purchases current when they renew, expire, or change outside your app.
What the connection provides
Nuxie can read apps and bundle IDs, in-app purchases, subscription groups, configured prices, introductory offers, transaction history, and subscription status. Use this connection to bring store context into a Task as well as to configure your catalog.
Compare the monthly and annual subscription offers for our running app, including their introductory offers.
The connection supports store-side data and notifications. Your app still needs the iOS purchase integration to display Product information and run checkout.
Credentials
Create an Apple API key
Create an App Store Connect API key with access to the app.
Enter the credentials in Nuxie
Open the app’s settings and choose Manage in App Store Connect. Enter:
| Field | Value |
|---|---|
| Issuer ID | The issuer identifier for your Apple account. |
| Key ID | The identifier of the API key. |
| Private key | The complete contents of the downloaded .p8 key. |
Load the available apps
Choose Save & Continue to save the connection and load the apps available to that account.
The key’s permissions determine which apps and operations Nuxie can access. Connecting accounts covers connection management and access.
Products
Under Select Your App, choose the Apple app with the matching bundle ID, then choose Connect. You can also enter its numeric Apple App ID, found in App Store Connect under App Information. Nuxie checks the listing against the connected account and starts syncing its Products.
Open Products to review the imported catalog. Use Sync Products again after changing products or offers in App Store Connect. Each Nuxie Product’s App Store identifier must match its StoreKit product identifier. A Product’s display name is not its store identifier.
Connect Products to the Features they grant. Monthly and annual plans can both unlock premium, for example. The paywall’s separate placements select which plan to purchase.
StoreKit supplies localized prices and current offer information in the app. Use Product bindings rather than putting a fixed currency amount in an image or unrelated text.
Server notifications
App Store Server Notifications report changes that happen without the app open. Linking the Apple app gives Nuxie its bundle ID and creates separate notification targets for test and live purchases. Saving credentials alone does not configure Apple’s server URLs.
Nuxie accepts signed Version 2 notifications and checks that the bundle ID and environment match the target. Apple Sandbox maps to Nuxie test; Production maps to live. Apple’s production and sandbox server URL settings determine where it sends each notification; see Apple’s notification settings.
Notifications report changes such as renewals, expiration, refunds, and billing recovery. Purchase and subscription state determines the resulting access; receiving a notification is not itself a new purchase by the customer.
Testing
An Apple test notification checks endpoint delivery. A sandbox purchase exercises checkout, customer association, and Feature access. Use Verify iOS purchases to test purchasing and restoration in the integrated app.
Keep the app’s SDK key, purchase environment, and notification target aligned. A sandbox transaction belongs in Nuxie’s test environment, even when the app also has a live catalog.
Troubleshooting
| Symptom | Check |
|---|---|
| The connection cannot authenticate | Issuer ID, Key ID, the complete .p8 contents, and whether the key is still active. |
| An app or Product is missing | The key’s app access, selected bundle ID, and exact store Product identifier. |
| A notification is rejected | Version 2, the generated endpoint, and the notification’s bundle ID and environment. |
| A test notification succeeds but access does not change | Run an actual sandbox purchase; a test notification does not create one. |
| Checkout succeeds but a Feature stays unavailable | The customer identity, purchase synchronization, and Product-to-Feature mapping. |
For delivery and retry behavior, see Webhooks.