- URL: https://asomaster.app/docs/app-store-connect/ - Updated: 2026-10-27 - Summary: Create an App Store Connect API key, find the Issuer ID and Key ID, and connect it to ASOMaster to read your keyword field, analytics and publish listings. # App Store Connect Updated 27 October 2026 Connecting your App Store Connect account is optional. Without it, ASOMaster reads your public App Store page. With it, the app also sees what only you can see, and can fill a new version for you. ## What a connection adds - **Your apps, listed for you.** Add app shows every app in the account, including unreleased ones, with Add and Add all. - **Your keyword field.** The hidden 100-character field is read for every locale, so scoring and Listing Studio work from your real listing. - **Store analytics.** Impressions, product page views and downloads by source and territory, from Apple's Analytics Reports. - **Publishing.** Listing Studio can create or fill the editable version and write the name, subtitle, keyword field and other text for every language you localized. It never submits the version for review; you do that in App Store Connect when you're ready. ## Create an API key 1. Sign in to [App Store Connect](https://appstoreconnect.apple.com/access/integrations/api) as the Account Holder or an Admin and open **Users and Access › Integrations › App Store Connect API**. On the Team Keys tab, request access first if Apple asks. 2. Click the add button, name the key (for example "ASOMaster") and choose the **App Manager** role. App Manager can read and edit app metadata; a lower role can read but can't publish. 3. Click **Download API Key**. You get a file named `AuthKey_XXXXXXXXXX.p8`. Apple lets you download it only once, so keep it somewhere safe. 4. Note two values from the same page: the **Issuer ID** (a UUID shown above the keys list, with a Copy button) and the key's **Key ID** (10 letters and digits, also part of the file name). ## Connect it in ASOMaster 1. Open **Settings › Store consoles** (or the Store consoles step of the setup guide) and choose App Store Connect. 2. Drop the `.p8` file. If it's in Downloads or on the Desktop, the app offers it for one click. The Key ID fills in from the file name. 3. Paste the Issuer ID, optionally add a label, and connect. ASOMaster tests the key and tells you how many apps it can see. Have apps in several developer accounts? Connect each one; apps are grouped by account. ## Where the key goes - The private key is stored in your operating system's keychain (macOS Keychain or Windows Credential Manager), never in a plain file and never on our servers. - It is used only to sign short-lived tokens, and those tokens are sent only to `api.appstoreconnect.apple.com`. The client refuses any other host and doesn't follow redirects. - Agents connected through MCP pass the key as a file path; the secret is never returned to them. ## How publishing works In Listing Studio, Publish creates the next editable version (or fills the one you already have), writes the chosen text for each language, and adds languages the version doesn't have yet. You see a report of what changed per language. Submitting for review stays in your hands, in App Store Connect. When an agent asks to publish through MCP, it must quote your explicit approval, and the app then shows you a native confirmation dialog. See [MCP safety](https://asomaster.app/docs/mcp/#safety). ## Troubleshooting **"Issuer ID is a UUID"** Copy the Issuer ID from the top of the App Store Connect API page, not the Key ID or your team ID. It looks like `57246542-96fe-1a63-e053-0824d011072a`. **The key connects but publishing is refused** The key's role is too low. Create a new key with the App Manager role (or Admin) and connect that one instead. **I lost the .p8 file** Apple can't send it again. Revoke the old key in App Store Connect, create a new one and reconnect. **Analytics say reports are on the way** The first time, ASOMaster asks Apple to start producing reports for the app. Apple prepares them in the background, which can take a day or more. Click Check again later.