Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Playlists list for a user not updated

Playlists list for a user not updated

Hi !

Seems today/yesterday, more and more of our app users are getting weird behavior when we are listing the Spotify user playlists.

Some of the Spotify user playlists are not returning anymore when requesting the Spotify API and some others are returned but to an old version... 

 

Are you aware of any issue relative to the endpoint User Playlists ?

Reply
2 Replies

This might explain the issue you are seeing. It looks like Spotify changed a couple of things in their Web API.  First of all, they used to always include an Owner object in the JSON response for each playlist. I would use the user ID inside the Owner to create the endpoint like this:

 

/v1/users/{user_id}/playlists/{playlist_id}

 

In the last couple of days (not sure exactly when), curated playlists no longer contain an Owner object. It is now set to null.  Also, they simplified the endpoint for fetching a playlist so that it no longer requires the owner's user ID. Now you can replace the above endpoint with:

 

/v1/playlists/{playlist_id}

 

I just made this change today in my software and it resolved these issues. I hope this helps.

Thank you for these precious information.

Unfortunately it's already the endpoint we are using since a while now...

The issue seems to be on the /v1/me/playlists first with missed elements not returned here and then in the tracklist itself, using /v1/playlists/{playlist_id}...

But as it's only happening time to time and for few users, hard to reproduce and report here 😕

Suggested posts