Docs
Connect App Store Connect
Connect App Store Connect with an API key: issuer ID, key ID, and the .p8 private key — plus how the encrypted vault protects them.
AppBoard talks to Apple through the App Store Connect API. You generate a team API key once, hand AppBoard three values, and every app on the account becomes available to manage.
What you need
| Value | Where it comes from |
|---|---|
| Issuer ID | Shown at the top of the Keys tab in App Store Connect. |
| Key ID | Assigned to the API key when you create it. |
| Private key (.p8) | The key file you download — Apple lets you download it once. |
Generate the API key
- In App Store Connect, open Users and Access → Integrations → App Store Connect API.
- Create a new key. Give it a name and an access role that can read and edit app metadata (Admin or App Manager).
- Copy the Issuer ID and the new key's Key ID.
- Download the .p8 private key file and keep it — Apple only offers the download once.
Heads up:the .p8 file can't be re-downloaded. If you lose it, revoke the key in App Store Connect and generate a new one.
Add the connection in AppBoard
- Open your workspace and start a new App Store connection.
- Paste the Issuer ID and Key ID, then upload the .p8 file. AppBoard encrypts all three in the vault before they touch the database.
- Save. AppBoard verifies the key and imports the apps it can see on the account.
If this is your first credential, AppBoard walks you through creating the encrypted vault. The vault must be unlocked for AppBoard to use the key — while it is locked, store calls are rejected and the UI prompts you to unlock.
After it connects
Your apps land on the dashboard with their current version. From there you can edit listings per language, manage screenshots, and push version localizations back to Apple. Nothing is sent to the App Store until you publish it.