Fastlane documents the API key flow in App Store Connect API. The Application Platform stores the same data as organization credentials and injects it into project CI.
1. Create an API key in App Store Connect
- Sign in to App Store Connect.
- Open Users and Access → Integrations → App Store Connect API (labels may vary slightly).
- Create a new key with an appropriate role (often App Manager or Developer, depending on your Fastlane actions).
- Download the private key (
.p8) once and store it securely. Apple does not show the secret again.
From the same screen copy:
- Key ID
- Issuer ID (UUID for the organization / API)
2. Developer Team ID and team name
- Developer Team ID (10 characters, e.g. from the Developer portal under Membership) identifies the team used for signing and App Store Connect operations.
- Team name is the human-readable team name as shown in App Store Connect / the Developer portal; Fastlane uses it for context and logging.
3. Fields in the Application Platform
When you create an App Store credential in the frontend, enter these five values:
| Platform field | Source |
|---|---|
| App Store key ID | Key ID from App Store Connect |
| App Store issuer ID | Issuer ID from App Store Connect |
| App Store key value | Full contents of the .p8 file (including -----BEGIN PRIVATE KEY-----) |
| Developer team ID | Team ID from the Apple Developer portal |
| Team name | Display name of the team |
This matches what Fastlane expects for app_store_connect_api_key and variables such as APP_STORE_CONNECT_KEY_ID and APP_STORE_CONNECT_KEY_ISSUER_ID; CI materializes the private key from the stored material, similar to Fastlane’s key_filepath / key content approach.
4. Security
- Do not expose
.p8material or issuer/key IDs publicly; restrict organization credentials to trusted admins. - Rotate keys if compromise is suspected and update the platform entry.