Undocumented playlist context type `playlist_v2`?!

[loisaidasam]

Issue noticed today, on 21 August 2018.

Endpoint(s):

• GET /v1/me/player/recently-played (docs)

Scope(s):

• Authed

Expected behavior:

The response should be (is) a list of play history objects, each of which includes a context object.

According to the documentation, valid values for the context object type are:

The object type, e.g. “artist”, “playlist”, “album”.

But it looks like the last time our system received a type value of playlist was on 13 July (over a month ago).

I stepped in to see what was going on and saw that contexts now look like this:

{
  "href": "https://api.spotify.com/v1/playlists/0AfmL9xTnmVPsb97pA31w6",
  "type": "playlist_v2",
  "uri": "spotify:playlist:0AfmL9xTnmVPsb97pA31w6",
  "external_urls": {
    "spotify": "https://open.spotify.com/playlist/0AfmL9xTnmVPsb97pA31w6"
  }
}

and as you can see, we're getting type of playlist_v2, which is not documented anywhere. What does this mean? Can we expect it to change again? Please advise.

Note, when searching for other people talking about this, I also saw this comment

[JoaaoVerona]

AFAIK yes, it's not documented; but it's because of the migration to shorter playlists IDs. Notice that, previously, with type: "playlist", the URIs of playlists would be like uri: "spotify:user:{USER}:playlist:{PLAYLIST}"; but, with type: "playlist_v2", the URIs are like uri: "spotify:playlist:{PLAYLIST}".

[loisaidasam]

Good point @BloodShura , thanks.

Would love to see this reflected in the documentation, or at least in that blog post! 🙀

[arirawr]

We're looking into this - thanks for the report.