Update: Due to technical issues, we have rolled back the change originally scheduled for 11th September 2018. We will communicate a new date for the change as soon as we have one.

Spotify URIs are unique, static identifiers returned and consumed by several parts of our APIs in order to represent a particular Spotify content object, such as a track, an album, a playlist, a user etc.

On the 11th September 2018 we will roll out a change across all our APIs to simplify the URIs used to represent playlist objects. Instead of a long URI such as spotify:user:spotify:playlist:37i9dQZF1DZ06evO3OC4Te, you will now get the more succinct but still unique spotify:playlist:37i9dQZF1DZ06evO3OC4Te.

In tandem with this change, we are also releasing a set of simplified URLs for our Playlist Web API endpoints. The usage, functionality and response objects are identical, but the URLs are more concise and follow the new URI structure more closely.

You can see the full list of URLs in the table below:

Endpoint Usage
/v1/playlists/{playlist_id}/tracks Get/Add/Remove/Reorder/Replace a playlist’s tracks (depending on HTTP method)
/v1/playlists/{playlist_id} Retrieve or update a playlist’s details (depending on HTTP method)
/v1/me/playlists Create a Playlist (POST only)
/v1/playlists/{playlist_id}/images Get/Upload a Playlist Cover Image (depending on HTTP method)

These updated endpoints are available with immediate effect for use in your applications, but until the URI change takes effect on the 11th September 2018 all URLs returned from the APIs - for example when a playlist resource is surfaced as part of a result from the search web api - will point to the existing, more verbose URLs. After the 11th September 2018 all playlist resource URLs across all endpoints returned will use the new structure, but the old URLs will continue to function until further notice.

If you are not relying on the structure of the playlist URIs - i.e. you are not parsing them in order to determine the playlist owner - then the changes made on 11th September 2018 will not impact your application and you need take no immediate action, although you are encouraged to move over to the newer, more simplified URL structure as soon as is convenient.

If you are relying on the structure of the playlist URIs you must take immediate action to ensure that this change does not impact the functionality of your application. If you are parsing the URI to determine the playlist owner, you should instead read this information from the owner user object available as part of both the full and simplified playlist object model.

Let us know if you have any questions over on the spotify/web-api GitHub.


The Spotify for Developers Team