Playlist API Endpoint inconsistency

nickel91 — Mon, 10 Mar 2025 14:57:47 GMT

TL;DR: If a playlist like https://open.spotify.com/playlist/37i9dQZF1DZ06evO3FRpH0 is queried with the id using the playlist API endpoint it shouldn't say 404 since other Endpoints explicitly give out a href for that resource, but rather give the meta information like name, description etc. (Without "track" information, since that is obviously why they deactivated it in the first place.)

My Question or Issue

My App is using https://api.spotify.com/v1/playlists/{playlist_id} (Documentation) to get information about a users playlist.

I am mostly interested in the Name and Description of the Playlist as well as the follower count. Having the tracks is nice but not really necessary.

Since Playlists made by Spotify and Spotifydiscover have been excluded recently (Blogpost: Changes to Web API) my app isn't functioning properly.

I get that Spotify doesn't want to include all tracks for public lists due to security reasons, but just leave them blank then and provide the other fields. This would actually make sense since the recently played endpoint (Documentation) actually provides a playlist with href to the playlist endpoint (see attached image)

But if the playlist is some auto generated like "Your Top Songs 2024" or the example in the TL;DR, it will only reply 404 - Resource not found.

topic Playlist API Endpoint inconsistency in Spotify for Developers

Playlist API Endpoint inconsistency