Announcements

Help Wizard

Step 1

NEXT STEP

Issue with Reordering Tracks in Playlist via API - Action Not Performed

Solved!

Issue with Reordering Tracks in Playlist via API - Action Not Performed

 

 

 

Plan: 
Both (Free & Premium) 
Platform:
WebAPI. 
Country: 
Pakistan / USA / Netherland

Hello Spotify Developer Community,

I am encountering an issue with the Spotify Web API where I attempt to reorder tracks within a playlist but the action doesn't seem to be performed, despite getting a successful response. Here are the details:

Endpoint: PUT https://api.spotify.com/v1/playlists/<PLAYLIST_ID>/tracks

Authorization: Bearer Token (Token is active and has the necessary scopes)

Request Body:

{ "range_start": 16, "insert_before": 2, "range_length": 5 }

Expected Behavior: The 5 tracks starting from position 17 should be moved to begin at position 3 in the playlist.

Actual Behavior: The API returns a successful response with a snapshot_id, suggesting that the request was successful. However, when I check the playlist, the tracks have not been reordered as expected.

Troubleshooting Steps Already Tried:

  1. Double-checked the token permissions.
  2. Verified the playlist ID and track positions.
  3. Made multiple attempts with different values.

I'm puzzled as to why the response indicates success but the playlist remains unchanged. Has anyone else experienced this? Any insights or suggestions on what might be going wrong or what I should try next would be greatly appreciated.

Thank you!

 

Reply

Accepted Solutions
Marked as solution

We have an update on this shared here.

View solution in original post

3 Replies

Something seems to be wrong with their endpoint after an update they pushed. One of the moderators said they would look into this in the report below:

https://community.spotify.com/t5/Spotify-for-Developers/Update-Playlist-Items-endpoint-returning-wro...

Hey LeSqueed,
Thanks for sharing your experiences and the ticket link. It's helpful to know this issue is recognized and being addressed, though the delay is surprising. I'll keep an eye on your ticket for any updates and hope for a swift resolution. Appreciate your insights and updates.!!

Marked as solution

We have an update on this shared here.

Suggested posts