You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and I went to the Spotify Web API site and found that the url must be formed like this:
So I think that is needed to specify that an userId is also required to do the request properly.
Because currenlty in your docs this is not being specified:
First attempt without userId gave me a 404 error Second attempt with userId gave me a 201
Desktop (please complete the following information):
OS: Windows 10 Pro
Browser: Google Chrome
Version: 80.0.3987.163
The text was updated successfully, but these errors were encountered:
This is something that needs to be done across several endpoints (get a playlist, add items to a playlist, change playlist details, get a playlist cover image, get playlist items, remove items from playlist, reorder playlist times, replace playlist items, upload cover image.
Since it's a breaking change it needs some extra work to make sure existing integrations will work fine.
Hello this is my first time posting an issue on github. I don't know if here is the place to report something like this but I had an issue with the API call addTracksToPlaylists. I was trying to using it with the params:
playlistId and uri's list as it was told in the documentation
and the API wrapper builded this url: https://api.spotify.com/v1/users/[**playlistId**]/playlists/spotify:track:5cB9BlseQteklXaJjRtZti,spotify:track:2u6CBCGo8outw3ThHk4c4l,spotify:track:3dq0YBLnSElFSWETquqtxP,spotify:track:3PS7vZHBOB3rT70CUYHagZ/tracks
and I went to the Spotify Web API site and found that the url must be formed like this:
So I think that is needed to specify that an userId is also required to do the request properly.
Because currenlty in your docs this is not being specified:
First attempt without userId gave me a 404 error
Second attempt with userId gave me a 201
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: