Spotify Web API
/v1/playlists/{id}/tracks stops working on Development Mode apps
Stopped workingSubscribe to Spotify Web APIShare
On February 11, 2026, the endpoint /v1/playlists/{id}/tracks stops working for Development Mode apps. Calls made to this endpoint by affected applications fail after that day. The playlist track management endpoints were renamed from tracks to items.
Calls it hits
/v1/playlists/{id}/tracks
What to use instead of these calls
Call /v1/playlists/{id}/items instead for Development Mode apps.
In Spotify Web API's words
The playlist track management endpoints have been renamed from /tracks to /items
Facts
- API
- Spotify Web API
api.spotify.com - Kind
- Removal
- Announced
- February 6, 2026
- Takes effect
- February 11, 2026
- Calls after that day
- Fail
- Who it affects
- Development Mode apps
- Source
- Announcement
- Last updated
- Verified
- , against Spotify Web API's own pages
Questions
When does this change take effect?
Calls to /v1/playlists/{id}/tracks on Spotify Web API stopped working on February 11, 2026.
What happens to calls after February 11, 2026?
They have failed since February 11, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Spotify Web API 5
-
GET /v1/audio-features*Removal Stopped working -
GET /v1/artists/{id}/related-artistsRemoval Stopped working -
GET /v1/audio-analysis/{id}Removal Stopped working -
GET /v1/recommendationsRemoval Stopped working -
GET /v1/tracksRemoval Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.