Cannot create MusicKit key — "There are no identifiers available that can be associated with the key"

I'm trying to create a Media Services (MusicKit) key to use the Apple Music REST API from a server-side application. When I navigate to Keys → (+) and select Media Services (MusicKit), I receive the error: "There are no identifiers available that can be associated with the key."

I've already tried the suggested fix of registering an App ID with MusicKit capability enabled (Identifiers → + → App IDs → App, with MusicKit checked under App Services). The identifier shows MusicKit as enabled when I view it, but returning to key creation still shows the same error.

Steps taken:

  • Registered a new App ID (com.turnkeycorrections.musickit) with MusicKit capability enabled
  • Hard-refreshed the Keys page after registration
  • Verified the identifier saved correctly

Account details:

  • Apple Developer Program (Organization)
  • Role: Account Holder / Admin

My use case is server-to-server only — I just need a developer token to call the catalog search, charts, and artist endpoints. No user authentication required.

Has anyone resolved this, or is there a step I'm missing to unlock MusicKit key creation?

Answered by DTS Engineer in 888711022

Thanks for the detailed report. The symptom you're describing — App ID with MusicKit capability shows as enabled, but the Media Services key creation says "no identifiers available" — is a clear sign that the Developer Portal has two different identifier paths for MusicKit, and the path you took isn't the one the Media Services key flow uses.

The two paths:

  • App ID with MusicKit capability — for native iOS/macOS apps that link the MusicKit framework on-device. The App ID enables MusicKit usage for the app build chain. Documented on the MusicKit Services help page.
  • Media ID — for server-side use of the Apple Music REST API via developer tokens. This is the identifier the Media Services key picker requires. Documented on the Create a media identifier and private key help page.

Your server-to-server use case (developer token for catalog search, charts, artist endpoints) is the Media ID path.

The fix:

  1. Go to Certificates, Identifiers & Profiles → Identifiers → click the (+) button
  2. Select Media IDs (not App IDs) — this is the identifier type the Media Services key flow expects
  3. Enter a description (this displays as the app name to people requesting Apple Music access; not relevant for purely server-to-server use, but still required)
  4. Enter a reverse-domain identifier (for example, media.com.turnkeycorrections.musickit)
  5. Enable MusicKit (and any other Media Services you plan to use, such as Apple Music Feed or ShazamKit)
  6. Click Continue, then Register
  7. Return to Keys → (+) → select Media Services — the new Media ID will appear in the picker

The dependency is also called out on the Create a private key help page: "If the Media Services checkbox is disabled, you need to register a media identifier first."

The App ID with MusicKit capability you already created can stay where it is — it's harmless. It just isn't what the Media Services key flow filters for.

Once you have the .p8 file from the key, the key ID, and your team ID, you can generate JWT developer tokens per the Generating Developer Tokens documentation.

Thanks for the detailed report. The symptom you're describing — App ID with MusicKit capability shows as enabled, but the Media Services key creation says "no identifiers available" — is a clear sign that the Developer Portal has two different identifier paths for MusicKit, and the path you took isn't the one the Media Services key flow uses.

The two paths:

  • App ID with MusicKit capability — for native iOS/macOS apps that link the MusicKit framework on-device. The App ID enables MusicKit usage for the app build chain. Documented on the MusicKit Services help page.
  • Media ID — for server-side use of the Apple Music REST API via developer tokens. This is the identifier the Media Services key picker requires. Documented on the Create a media identifier and private key help page.

Your server-to-server use case (developer token for catalog search, charts, artist endpoints) is the Media ID path.

The fix:

  1. Go to Certificates, Identifiers & Profiles → Identifiers → click the (+) button
  2. Select Media IDs (not App IDs) — this is the identifier type the Media Services key flow expects
  3. Enter a description (this displays as the app name to people requesting Apple Music access; not relevant for purely server-to-server use, but still required)
  4. Enter a reverse-domain identifier (for example, media.com.turnkeycorrections.musickit)
  5. Enable MusicKit (and any other Media Services you plan to use, such as Apple Music Feed or ShazamKit)
  6. Click Continue, then Register
  7. Return to Keys → (+) → select Media Services — the new Media ID will appear in the picker

The dependency is also called out on the Create a private key help page: "If the Media Services checkbox is disabled, you need to register a media identifier first."

The App ID with MusicKit capability you already created can stay where it is — it's harmless. It just isn't what the Media Services key flow filters for.

Once you have the .p8 file from the key, the key ID, and your team ID, you can generate JWT developer tokens per the Generating Developer Tokens documentation.

Cannot create MusicKit key — "There are no identifiers available that can be associated with the key"
 
 
Q