App Store Connect integration
Connect App Store Connect API keys in FlwKit to sync approved app versions and enforce block-type delivery compliance.
Overview
FlwKit can connect to App Store Connect so we only deliver block types that are confirmed in App Store-approved builds.
This integration is based on Apple App Store Connect API keys (.p8) and validates credentials before saving.
Prerequisites
- A FlwKit app in your dashboard
- Access to App Store Connect for the same iOS app
- An App Store Connect API key (
.p8) with required permissions - Your app bundle ID (for example
com.company.app)
Reference: RevenueCat guide for App Store Connect API key setup
Get your App Store Connect credentials
In App Store Connect, collect:
- Issuer ID
- Key ID
- Private key file (
AuthKey_XXXXXXXXXX.p8) - Bundle ID of the iOS app you want to connect
Apple only lets you download a private key file once. Store it securely before leaving App Store Connect.
Connect in FlwKit
- Open Settings → Integrations
- In App Store Connect, click Add new key
- Upload your
.p8file (or paste its content) - Enter Issuer ID, Key ID, and Bundle ID
- Click Connect App Store Connect →
FlwKit verifies credentials with Apple before saving.
Connected status
After connection, the card shows:
- Connection status
- Bundle ID
- Live version/build (when available)
- Last sync time
- Sync errors (if any)
You can also run Sync now to trigger a manual sync.
Troubleshooting
Invalid credentials
Re-check:
- Issuer ID and Key ID are exact
- Bundle ID matches the connected app
.p8key belongs to the same App Store Connect account/team
Sync errors after previously working
Common causes:
- API key revoked in App Store Connect
- Permissions changed
- App transfer/team change in App Store Connect
Disconnect and reconnect with a fresh key if needed.
Security
- Private key data is encrypted at rest
- Private key is never returned in API responses
- UI shows only masked key preview details where applicable