Skip to main content
The App Store Connect API key lets Qonversion read your app’s metadata directly from App Store Connect. We use it to:
  • Sync your in-app purchase catalog and prices using your app’s App Store ID.
  • Read your subscription grace period configuration.
With report access and your Vendor number, the key also lets Qonversion read sales reports for verified revenue reporting. Without this key, Qonversion cannot sync your App Store catalog and prices or read its sales reports.
This key is separate from the In-App Purchase API key, which is used for App Store Server API access and promotional offer signing. The In-App Purchase key cannot sync your catalog or sales reports, and the App Store Connect key cannot sign promotional offers.
Apple Ads has a separate connection: Connect with Apple for new connections and an Apple Ads API key for projects already connected with one. Neither App Store key on this page is an Apple Ads credential.

1. Make sure you have the right role

An Account Holder or Admin can generate a team API key. The role of the person generating the key is separate from the key’s Access setting. Choose App Manager access for product and price sync and subscription grace period settings. If you also use Verified revenue reports, choose Admin access for the same key and add your Vendor number in Qonversion. Contact your team’s Account Holder or Admin if you cannot generate a team key.

2. Open the App Store Connect API tab

  1. Log in to App Store Connect.
  2. Click Users and Access in the top navigation.
  3. Open the Integrations tab.
  4. Make sure the App Store Connect API sub-tab is selected (not “In-App Purchase”).

3. Generate a new key

  1. Click Generate API Key (or + if you already have keys).
  2. Give it a clear name, e.g. Qonversion.
  3. Set Access to App Manager for catalog and price sync. Choose Admin if you also use Verified revenue reports.
  4. Click Generate.

4. Copy the Key ID and Issuer ID, and download the .p8 private key

Everything you need lives on the same screen — copy the two identifiers and download the key file before leaving:
  • Copy the Key ID (10-character string in the row of your new key) — this is Key ID in Qonversion.
  • Above the table, copy the Issuer ID (UUID format, e.g. 57246542-96fe-1a63-e053-0824d011072a) — this is Issuer ID in Qonversion.
  • In the same row, click Download API Key to get the .p8 file.
Apple lets you download the .p8 file only once. Save it somewhere safe before continuing. If this key is already saved in Qonversion, losing your local copy does not require you to replace it.

5. Paste everything into Qonversion

  1. Open Qonversion Dash → Project Settings → Stores → Apple App Store.
  2. Under Credentials on file, open App Store Connect API key (Set up the first time, Edit once a key is saved):
    • Paste the Key ID in the Key ID field.
    • Upload the .p8 file in the Private Key field.
    • Paste the Issuer ID in the Issuer ID field.
  3. Click Save & verify.
The page shows which capabilities Apple confirmed for the key. Add your App Store ID on the Product sync row to sync that app’s catalog. For Verified revenue reports, add your Vendor number on that row.

Troubleshooting

”Failed to verify credentials” — HTTP 401 / NOT_AUTHORIZED

  • Make sure you pasted the Key ID, not the key name.
  • Make sure the Issuer ID is from the App Store Connect API tab, not the In-App Purchase tab.
  • Make sure the .p8 file matches the Key ID you pasted.

Product sync says the key cannot sync products

Create a new team key with App Manager access for product sync, or Admin if you also use Verified revenue reports. Save it with Edit, then follow the replacement steps below before revoking the old key.

Lost the .p8 file

Apple does not let you re-download the file. If the key is already saved in Qonversion and still works, no action is needed. To replace it, keep the old key active, generate a new team key, and save its .p8, Key ID, and Issuer ID with Edit → Save & verify. Confirm the displayed Key ID matches the new key, it shows Verified, and What this key unlocks confirms the capabilities you use. If you use this key for App Store Server API requests, ask Qonversion support to confirm the replacement before revoking the old key. Revoke the old key after these checks and any needed support confirmation.

What’s next?

To finish setting up the App Store connection: