Connect App Store Connect

Asomium talks to App Store Connect through Apple’s official API, with a key you create. It needs three things from one page on Apple’s site: the Issuer ID, the Key ID and the .p8 private key file.

Inside the app, Settings → App Store Connect → Show me where… opens the same steps with a labelled sketch of Apple’s page.

Generate an API key

You need the Admin or Account Holder role on the team.

1. Sign in to App Store Connect.
2. Users and Access → Integrations tab → App Store Connect API in the left column → Team Keys. The first time, the Account Holder has to click Request Access.
3. Click Generate API Key (or +). Any name works, for example Asomium.
4. Under Access, choose:
   • App Manager — enough for metadata, screenshots, builds and Submit. The minimum we recommend.
   • Admin — if you also want the Revenue tab. Apple only serves sales reports to Admin, Finance or Sales keys.
5. Click Generate.

Now collect the three values:

	Where it is
1 · Issuer ID	Above the table of keys, with a Copy button. Looks like 57246542-96fe-1a63-e053-0824d011072a. The same for every key on the team.
2 · Key ID	In the new key’s row. Ten characters, like 2X9AB7C4DE.
3 · .p8 file	Download API Key in the same row. Apple lets you download it once and keeps no copy — store it somewhere safe. The file is named AuthKey_<Key ID>.p8.

Use a Team key. Individual keys carry one user’s permissions and can’t reach sales and finance reports.

Connect Asomium

1. Open Asomium → Settings → App Store Connect (the welcome tour asks for the same three things on first launch).
2. Paste the Issuer ID.
3. Click Choose… and pick the .p8 file, or drop it on the row. Asomium reads the Key ID from the file name and fills it in; type it yourself if you renamed the file.
4. Click Verify & save. Asomium asks Apple for one app with the key, and saves the key only if it works — a typo never replaces a working key. (2.0.0 labelled the button Validate and saved first; update to 2.1.)

The key is stored in your macOS Keychain and is only ever sent to api.appstoreconnect.apple.com.

For the Revenue tab, also fill in Vendor # on the same screen — it is in App Store Connect → Payments and Financial Reports, in the page footer.

If Apple rejects the key

• “Apple didn’t accept this key” (401) — the Key ID, Issuer ID and .p8 don’t belong together, or the key was revoked. The usual cause is an Issuer ID and a Key ID pasted into each other’s field.
• “The API key isn’t allowed to do this” (403) — the key works but its role is too low. Sales reports need Admin, Finance or Sales.

Switching to a different key or team

Settings → App Store Connect → Use a different key…, enter the new values, Verify & save. Your current key keeps working until the new one has been verified. Then revoke the old key on App Store Connect.

A key belongs to one team. After switching teams, apps you imported from the old team stop syncing: import the new team’s apps, or give a single app its own key under that app’s Settings tab.

What Asomium calls

The same endpoints the App Store Connect website uses:

• GET /v1/apps — your app list
• GET /v1/apps/{id}/appStoreVersions — version state
• GET /v1/appStoreVersionLocalizations — metadata per locale
• PATCH /v1/appStoreVersionLocalizations/{id} — write back edits
• POST /v1/reviewSubmissions — submit for review
• GET /v1/salesReports — the Revenue tab