Updating API Keys for App Store Connect

Rotate or replace the App Store Connect API key used by Statused without deleting your apps or workflows.

This guide walks you through replacing the App Store Connect API key connected to Statused. Use it when you rotate keys, when a key was revoked in App Store Connect, or if Apple makes breaking changes to their API, rejecting your current key.

Updating a key keeps everything else in place: your apps, workflows, and destinations stay exactly as they are.

Before You Start

You'll need Admin role permissions in App Store Connect to generate a new key. If you don't have this access, loop in your App Store Connect Admin.

Don't revoke the old key yet

Keep your current key active until the new one is saved in Statused. Revoking it first means monitoring stops until the update is complete.

Generating a New API Key

Head to App Store Connect and select the same organization your apps belong to from the top-right dropdown.

Navigate to Team Key settings

Go to Users and Access › Integrations › App Store Connect API › Team Keys.

Generate the key

Click the button, give your key a descriptive name like "Statused API Key", and choose the Admin, App Manager, or Developer role. See Creating API Keys for details on which roles work.

Download and copy the IDs

Download the private key file (.p8) right away — this is your only chance to download it. While you're on this page, also copy the Issuer ID (shown at the top of the page) and the new key's Key ID.

Updating the Key in Statused

Open your API Keys

Go to your Statused dashboard and open API Keys.

Choose the key to update

Find your App Store Connect API key, open the menu next to it, and select Update credentials. If Apple is rejecting the key, you can instead click the Update key button shown next to it. You can rename the key in the same dialog; changing only the name doesn't require new credentials.

Upload the new credentials

Upload your new .p8 file and enter the new Key ID and Issuer ID. All three are required together when replacing credentials.

Save

Click Save Changes. Statused verifies the new key before saving anything.

That's it! Monitoring continues with the new key, and your apps and workflows are untouched.

Once the update succeeds, you can safely revoke the old key in App Store Connect.

How Verification Works

Before saving, Statused checks that the new key:

Authenticates with Apple. If it doesn't, you'll see an error and nothing changes. Double-check that the .p8 file, Key ID, and Issuer ID all belong to the same key.
Can access every app with active workflows. Statused confirms the new key can see each app registered under this API key that has at least one active workflow. If any are missing, the update is rejected and Statused lists the apps it can't access.

If apps are missing, make sure the new key was created in the same App Store Connect organization as those apps, then try again.

When Apple Rejects Your Key

If Apple starts rejecting your key (for example, because it was revoked in App Store Connect), Statused shows a warning next to it on your API Keys page and pauses status checks for every app that uses it. This prevents repeated failed requests against Apple's API.

While paused, Statused rechecks the key periodically. Checks resume automatically as soon as Apple accepts the key again, or immediately after you update it with new credentials.

Status changes that happen while checks are paused aren't detected until monitoring resumes. Update the key as soon as you see the warning to avoid missing notifications. We'll also notify you via email whenever this happens.

Where to go from here

Need help? Reach out and we'll get you sorted.

Updating API Keys for App Store Connect

On this page