App Store Connect: listing, reviews, and sales

Connecting App Store Connect lets Appwin read your app's App Store data: metadata, reviews, sales.

This is read access in the common case. The permission level you grant is still your choice, and the key has as many rights as the role you assign - hence the recommendation below.

Settings → Projects → your app → Integrations → App Store Connect.

1. Create the API key (.p8)

You need to be Account Holder or Admin to see the Integrations tab.

  1. 1

    Open the App Store Connect API

    In App Store Connect: Users and Access → Integrations tab → App Store Connect API.

    App Store Connect Integrations tab, API section.

  2. 2

    Create the key

    + button → name it (e.g. "appwin") → pick a role → Generate.

    Creating an App Store Connect API key.

    Which role

    RoleWhat it allowsRecommendation
    DeveloperRead metadata and reviewsEnough for ASO
    FinanceRead sales reportsNeeded for store revenue
    App ManagerEdit listingsOnly if you want to publish from Appwin
    AdminEverythingAvoid

    Principle: grant the minimal role for what you plan to use. You can create several keys with different roles, and revoke one without touching the others.

  3. 3

    Download the .p8

    Click Download on the created row: the AuthKey_XXXXXXXXXX.p8 file downloads.

    Downloading the API key .p8 file.

    The .p8 downloads only once. Apple does not regenerate it. Lost the file? Revoke the key and create another.

  4. 4

    Import it in Appwin

    Use Import a file: Appwin reads the .p8 and often derives the Key ID from the file name.

    Importing the .p8 file into Appwin.

2. Collect the key identifiers

Still on the API Keys page. The private key is the contents of the .p8 already imported in step 1 (BEGIN / END lines included).

  1. 1

    Issuer ID

    UUID shown above the keys table. Same for every key on the account; it appears only after the first key is created. It tells Apple which App Store Connect account is calling.

    Issuer ID highlighted above the API keys list.

  2. 2

    Key ID

    Table column (or the AuthKey_XXXXXXXXXX.p8 file name fragment). Specific to this key. If you imported the file in step 1, Appwin often derives it for you.

    Key ID highlighted in the API keys table.

3. Identify your app

These values tie the key to your app, not the account in general.

  1. 1

    App ID (Apple ID)

    In Apps → your app → General → App Information, the "Apple ID" field (10 digits). It is also the number in the /apps/1234567890/ URL.

    Do not confuse it with the Appwin App ID (the SDK one): same name, two different notions.

    Apple ID (App ID) highlighted in app information.

  2. 2

    Bundle ID

    Still in App Information: the Bundle ID. Same value as Bundle Identifier in Xcode. Optional for Appwin, useful to cross-check with other integrations.

    Bundle ID highlighted in app information.

  3. 3

    Vendor Number (sales)

    In Payments and Financial Reports, top left (8 digits). Only needed for sales reports; without it, metadata and reviews still work.

    Vendor Number highlighted in Payments and Financial Reports.

4. Enter them in Appwin

FieldValue
App ID1234567890
Bundle IDcom.yourstudio.yourapp (optional)
Issuer IDaaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee
Key IDXXXXXXXXXX
Private keyContents of the .p8
Vendor Number87654321 (for sales, optional)

What it unlocks

DataMinimal role
Metadata, screenshots, keywordsDeveloper
Reviews and ratingsDeveloper
Sales and revenue reportsFinance

Security

Integration keys are encrypted at rest in the database. They are never returned in clear text to the dashboard: once saved, a key shows masked and can only be replaced.

If you suspect a leak, revoke the key from App Store Connect - revocation is immediate on Apple's side, regardless of what is stored at Appwin.

Troubleshooting

SymptomLikely cause
"Authentication failed"Wrong Issuer ID or Key ID
"Invalid private key"Truncated .p8: BEGIN/END lines must be included
Empty reviewsYour app has no reviews yet on the markets queried
Empty salesMissing Vendor Number, or a role without Finance permission
403 errorThe key's role does not cover the requested data

Next