Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Fix your damn API - Fields parameter not properly updating for next urls for playlist tracks

Fix your damn API - Fields parameter not properly updating for next urls for playlist tracks

Description:
When fetching playlist tracks with a fields filter via /v1/playlists/{playlist_id}, the next URL returned switches to /v1/playlists/{playlist_id}/tracks but incorrectly retains the original fields parameter. This causes empty responses because the fields don’t apply to the /tracks endpoint.

Expected:
next URL should adjust or remove fields to match the new endpoint.

Actual:
fields is left unchanged, breaking pagination.

This is just such a basic piece of the api. Fetching tracks from a playlist? Does your code have any tests at all? Also I know this was specifically broken at some point by spotify because I noticed this coming back from a project that was working perfectly with the same code previously.

Reply
0 Replies

Suggested posts

Type a product name