Adjust Spotify endpoints post deprecation notice

[OzGav]

References:
https://developer.spotify.com/documentation/web-api/references/changes/february-2026
https://developer.spotify.com/documentation/web-api/tutorials/february-2026-migration-guide

Changes Made

1. init.py

• Added ProviderFeature.PLAYLIST_CREATE to supported features (was previously missing)

2. provider.py — Library Operations

• library_add(): Consolidated 6 separate endpoints into single PUT /me/library with Spotify URIs (spotify:track:xxx,spotify:album:xxx, etc.)
• library_remove(): Consolidated 6 separate endpoints into single DELETE /me/library with Spotify URIs

3. provider.py — Playlist Operations

• get_playlist_tracks(): Changed response field from item["track"] to item["item"] for regular playlists (liked songs via me/tracks still uses item["track"]). Fixed cache duration typo (2600 → 3600 for actual 3 hours).
• remove_playlist_tracks(): Changed request body key from tracks to items, response field from item["track"] to item["item"]
• create_playlist(): Changed from POST /users/{id}/playlists to POST /me/playlists (no longer requires user ID lookup)

4. provider.py — Search

• Reduced page limit from 50 to 10 per API restrictions

5. provider.py — Album Tracks

• get_album_tracks(): Extended cache from default to 1 year (album track listings are immutable once released

[delatt]

Hi, thank you for all the work! I just wanted to let you know that I have hit the issue with Spotify renaming track to item and am unable to load my Playlists without fudging things. I know you said that you would keep this as a draft until the old API stops working but decided to comment here instead of creating a new issue.

[OzGav]

Personally I don’t encounter any issues with Spotify at the moment.. Maybe the API changes are being done regionally? Even though everything is working fine with the existing code it continued to work fine for me with the changes in this PR so I think it is safe…. I removed the changes to artist_toptracks as that is major and will put up another PR when people start reporting problems with that.

[delatt]

Looking at my Postman and Spotify responses:

• playlists/<id>/items returns items in items['item']: https://developer.spotify.com/documentation/web-api/reference/get-playlists-items
• playlists/<id>/tracks returns items in items['track']: https://developer.spotify.com/documentation/web-api/reference/get-playlists-tracks

The change from /tracks -> /items happened in #3436 but the response parsing was never updated so would have been broken from that point. So yeah, I think Spotify are gradually rolling things out (assuming nothing weird is going on with caching).

Maybe add a fallback or another case to find the item_key depending on what's in the response? This way both versions can be supported until the rollout is complete.