Get an App Store Connect API key
Configure the Team Key, Issuer ID and private key used by Store Sync.
Store Sync's Apple form uses a Team Key, not an individual key. Have access to the intended developer team before starting.
Get the key
- Open Users and Access → Integrations.
- If API access is unavailable, ask the Account Holder to request it.
- An Account Holder or Admin can open App Store Connect API → Team Keys and generate a key.
- Choose a name and the lowest role sufficient for your listing operations. Consult Apple's role permissions for the fields you will edit. Avoid choosing Admin just to bypass an error.
- Record the Issuer ID and Key ID, and download the private key. Keep the downloaded file private.
Team keys apply across the team's apps; selecting an app inside Store Sync does not restrict the key itself. For access changes, revoke the key and create a replacement. Apple API setup.
Match the plugin fields
| Plugin field | What to use |
|---|---|
| Issuer ID | Team issuer identifier from the API page |
| Key ID | Identifier of the selected Team Key |
| Private key | The downloaded .p8 file |
In extension Settings, select Apple, enter the Issuer ID and import the .p8 file. Standard AuthKey filenames can fill the Key ID automatically; check it before choosing Verify and save.
Do not use a signing certificate, provisioning profile or App Store password in these fields.
Check the target
After credentials are saved, retrieve your profile and preflight the target Apple ID, bundle ID and version. The version must accept the requested changes. Saving a draft does not submit it for review.
| Problem | Next action |
|---|---|
| Missing Integrations or key controls | Check your team and role with the Account Holder |
| Authentication fails | Check issuer/key pair, private key, revocation status and device time |
| App not found | Check team, Apple ID and bundle ID |
| Metadata or screenshot write fails | Check field permissions and editable version state; inspect partial results before retrying |
Rotate or revoke
Verify the new key in the extension first when performing a planned rotation. Then revoke the old key in App Store Connect after checking other tools that use it. If exposed, revoke promptly. Deleting the extension's local copy is not provider revocation.
Guide reviewed against plugin credential fields and Apple's API setup documentation on 2026-09-17. Console labels and role requirements can change. Back to Store Sync.
AppScreenshots Docs