MusicKit WebAPI - Can only get storefronts. All other endpoints return 500.

If I make a request to https://api.music.apple.com/v1/storefronts/us with the proper developer jwt token in the header, I receive the a successful response with a list of store fronts. If I remove the token, I do get back a 401 error.

If I call any other catalog base query, I am getting back a 500 error.

For instance: https://api.music.apple.com/v1/catalog/us/albums/310730204

returns a 500 error with the body being {"message":"An unexpected error occurred"}

I'm not sure what I can do to fix this. Please help.

Up vote post of MichaelHeiHei Down vote post of MichaelHeiHei
3.3k views
Posted by
MichaelHeiHei
Reply

  • Did it go away over time? If so, how long?

    —
    Chris_Sheridan
Add a Comment

Accepted Reply

Hello @MichaelHeiHei and @applebee1558

Thank you for reaching out about the 500 errors you’re receiving from the Apple Music App.

If both of you could submit a ticket to the Feedback Assistant, including a .har export from the network inspector showing the failed responses, it would be very helpful for us to diagnose this issue.

Thank you so much!

Posted by
Media Engineer
Up vote reply of Media Engineer Down vote reply of Media Engineer
Post marked as solved
Add a Comment

Replies

I'm getting the exact same issue. I'm wondering if this is an error with how I generate the JWT or if it's an Apple issue. The 429 token they posted on the page works fine though.

Posted by
applebee1558
Post not yet marked as solved Up vote reply of applebee1558 Down vote reply of applebee1558
Add a Comment

Hello @MichaelHeiHei and @applebee1558

Thank you for reaching out about the 500 errors you’re receiving from the Apple Music App.

If both of you could submit a ticket to the Feedback Assistant, including a .har export from the network inspector showing the failed responses, it would be very helpful for us to diagnose this issue.

Thank you so much!

Posted by
Media Engineer
Up vote reply of Media Engineer Down vote reply of Media Engineer
Post marked as solved
Add a Comment

I am seeing this as well with a freshly generated token.

Posted by
nokeeo
Up vote reply of nokeeo Down vote reply of nokeeo
Add a Comment

Same here with recent tokens.

Posted by
d_mchp
Up vote reply of d_mchp Down vote reply of d_mchp
Add a Comment

We are also experiencing this issue.

Posted by
PETERWOJCIECHOWSKI
Up vote reply of PETERWOJCIECHOWSKI Down vote reply of PETERWOJCIECHOWSKI
Add a Comment

Same issue with me

Posted by
quyquy
Up vote reply of quyquy Down vote reply of quyquy
Add a Comment

I am seeing the same issue. A token I generated this morning didn't work until about 1 hour after I generated it. Then it started working for a few hours, but newly generated tokens are all returning 500s.

Posted by
k05brady
Up vote reply of k05brady Down vote reply of k05brady
Add a Comment

Same error with me.

Posted by
Chris_Sheridan
Up vote reply of Chris_Sheridan Down vote reply of Chris_Sheridan
Add a Comment

I'm getting the same issue here. I generated some tokens in the last 2 days but I'm always getting the 500 error

Posted by
vadd98
Up vote reply of vadd98 Down vote reply of vadd98
Add a Comment

@Media Engineer I submitted a ticket to feedback assistant. Thanks. Do you know how long it might take to get a response?

Posted by
MichaelHeiHei
Up vote reply of MichaelHeiHei Down vote reply of MichaelHeiHei
Add a Comment

Greetings,

This issue is now resolved.

There was a server issue impacting some new MusicKit developer tokens which were getting rejected with HTTP error 500. This has now been rectified.

Sorry for the inconvenience, and please let us know if you encounter any other issue.

Posted by
apple82
Post not yet marked as solved Up vote reply of apple82 Down vote reply of apple82
Add a Comment

This issue has recurred. Previously working integrations with new developer tokens are return 500 responses. I even tried issuing myself an entirely new API key and unfortunately it still returns 500 responses. New Zealand region, if it makes a difference.

Apple service status page shows all-green.

It is a little disappointing that the API, the most mission critical interface for any developer, should break in this way just one month ago, then break again in apparently the same way just a few weeks later. This breaks the world for music apps. It makes developers of iOS music apps look like idiots, with frustrated users who cannot be given a good answer on what's gone wrong or when it'll be resolved.

When will this be fixed, please, and what steps are Apple taking to ensure that this does not break without Apple noticing again in future (e.g. ensuring that the Apple Service Status page correctly reflects a broken API condition)?

Thanks,

Posted by
adh1003
Up vote reply of adh1003 Down vote reply of adh1003

  • Hi @adh1003,

    Thanks for reporting this issue. There was an unrelated issue impacting some developers which has been resolved earlier today. Can you please try again if your issue has been resolved. If not could submit a ticket to the Feedback Assistant showing a sample CURL command (the HTTP request and the correspondingJWT)

    Thanks!

    —
    apple82

  • Thanks @apple82 - yes, it seems to be working again now.

    —
    adh1003
Add a Comment

Hi, I'm experiencing the same with a recent token...

https://api.music.apple.com/v1/storefronts/us is working

https://api.music.apple.com/v1/catalog/us/albums/310730204 is not, with error

{
    "message": "An unexpected error occurred"
}

Can you help ?

Posted by
RapMinerz
Up vote reply of RapMinerz Down vote reply of RapMinerz
Add a Comment