Skip to content

How to create an App Store Connect API key

An App Store Connect API key lets tools and scripts automate tasks in App Store Connect through Apple’s API. This guide covers who can create a team key, which role to give it, the private key you can download only once, and where to find the Issuer ID and the Key ID, based on Apple’s documentation as checked on November 18, 2026.

AppNorth ·

What an App Store Connect API key is

Apple’s App Store Connect API is a REST API that can automate certain tasks in App Store Connect. Every request needs a JSON Web Token (JWT), and you sign those tokens with an API key from App Store Connect. A key has two parts: a public portion that Apple keeps and a private key that you download.

There are two types. A team key gives access to all apps in your account, with permissions set by the role you choose. An individual key has the access and roles of the user who created it, and it can’t use the Provisioning endpoints, Sales and Finance or notaryTool. App Store Connect API keys only work with this API, not with other Apple services.

Who can create a team key

Before anyone can generate keys, the Account Holder must request access to the API. In App Store Connect, open Users and Access, then Integrations: the page opens with the App Store Connect API selected. Click Request Access, select the checkbox to agree to the terms and click Submit. Apple reviews and approves these requests case by case.

Team keys can be generated by the Account Holder or an Admin. Individual keys are different: by default, any user with the Account Holder, Admin, App Manager, Customer Support, Developer or Marketing role can generate one, unless an Admin or the Account Holder has removed that ability. Each user can have only one active individual key at a time.

Create a team API key step by step

Team keys suit tools that work across your apps, because they cover every app in the account. These are Apple’s steps, for the Account Holder or an Admin.

You can’t edit a key’s name or access level after you generate it. To change either, revoke the key and generate a new one. Team keys apply across all apps, so you can’t limit a team key to particular apps.

  • In Users and Access, click Integrations. The page opens with the App Store Connect API selected.
  • Click Team Keys, then Generate API Key. If you already have an active key, click the add button (+) instead.
  • Enter a name for the key. It is for your reference only and isn’t part of the key.
  • Under Access, choose the role that determines what the key can be used for.
  • Click Generate. The new key’s name, its Key ID and a download link appear on the page.

Choose the role for the key

The roles for API keys are the same ones that apply to users on your team, and the role decides which areas of the API the key can reach and which tasks it can perform. Keys with the Admin role have broad permissions, such as creating and deleting users. Whatever its role, a team key can access all apps.

Apple describes the roles like this in its role permissions. Choose the narrowest role that covers what your tool has to do, and keep Admin for tools that really need it.

App Store Connect roles as Apple describes them
RoleApple’s description
AdminSecondary contact for the team, with many of the Account Holder’s responsibilities and access to all apps
App ManagerManages all aspects of an app, such as pricing, App Store information, and app development and delivery
DeveloperManages development and delivery of an app
MarketingManages marketing materials and promotional artwork, and is contacted if Apple considers the app for featuring
SalesAnalyzes sales, downloads and other analytics for an app
FinanceManages financial information, including downloading reports and uploading tax forms
Customer SupportAnalyzes and responds to customer reviews on the App Store

Download the .p8 private key once and keep it safe

After you generate a team key, a Download API Key link appears next to it in the Team Keys list. The private key can be downloaded a single time: the link only appears while you haven’t downloaded it, and Apple doesn’t keep a copy. The file you get is a .p8 file named after the Key ID, in the form AuthKey_KEYID.p8.

Treat it like a password. Apple advises against sharing keys, storing them in a code repository or including them in client-side code. If a key is lost or compromised, revoke it immediately and generate a new one. A revoked key can’t be reinstated; keys revoked in the past 30 days are listed under Revoked.

Find the Issuer ID and the Key ID

A tool that signs tokens with a team key needs two values besides the .p8 file. The Issuer ID appears near the top of the App Store Connect API page in Integrations, with a Copy button next to it. The Key ID is listed for each key under Active: hover next to it and click Copy Key ID.

In the token, the Key ID goes in the kid header and the Issuer ID in the iss field; tokens are signed with ES256 and use appstoreconnect-v1 as the audience. Individual keys don’t use the Issuer ID: their tokens carry sub set to user instead. Tokens that expire more than 20 minutes in the future aren’t valid, except for some resources Apple lists.

What AppNorth needs from your key

AppNorth for Mac connects to App Store Connect with a team key. Its help asks for the App Manager role, which can edit App Store details, app pricing and subscription pricing without full admin access. Admin also works, but gives more access than AppNorth needs. Use a team key, not an individual key: AppNorth needs the Issuer ID, which only team keys have.

In AppNorth, open Settings → Integrations, click Connect on App Store Connect, paste the Issuer ID and the Key ID, choose the .p8 file and click Verify Connection. The key lets AppNorth publish reviewed listing changes and local prices for subscriptions and in-app purchases to App Store Connect. Approved changes go into a draft version, and AppNorth never submits your app for review. Store keys stay on your Mac, encrypted with a key kept in the macOS Keychain, and are only sent to Apple or Google.

Before you start

Who can create an App Store Connect API key?

Team keys: the Account Holder or an Admin, once the Account Holder has requested API access. Individual keys: by default, any user with the Account Holder, Admin, App Manager, Customer Support, Developer or Marketing role, unless that ability was removed.

Can I download the .p8 file again?

No. Apple lets you download the private key once and doesn’t keep a copy. If you lose it, revoke the key in App Store Connect and generate a new one.

Where do I find the Issuer ID?

Near the top of the App Store Connect API page, under Users and Access → Integrations, with a Copy button next to it. Team keys use it; individual keys don’t.

Should I use a team key or an individual key?

A team key covers all apps in the account and gets the role you choose. An individual key has its creator’s access and can’t use the Provisioning endpoints, Sales and Finance or notaryTool. Tools that ask for an Issuer ID, such as AppNorth, need a team key.

Which role does AppNorth need?

App Manager. It can edit App Store details, app pricing and subscription pricing without full admin access. Admin also works, but gives more access than AppNorth needs.

Can I change a key’s role later?

No. You can’t edit a key’s name or access level after you generate it. Revoke the key and generate a new one with the role you need.

Sources and further reading

AppNorth · macOS

Turn your research into a better listing.

€99.99 once. Lifetime license for 2 Macs, with updates included.

AI features use your own agent CLI: Claude Code, Codex, Gemini CLI, OpenCode, Cursor, Grok or Ollama. No AppNorth AI credits; your provider’s terms and costs still apply.

See AppNorth for Mac

macOS only. No free tier or trial. No voluntary refunds; legal exceptions apply. Read the refund policy.