[GH-ISSUE #234] createPlaylist #166

New issue

Closed

opened 2026-02-27 19:26:24 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 19:26:24 +03:00

Owner

Originally created by @rac-andreharry on GitHub (Aug 23, 2021).
Original GitHub issue: https://github.com/jwilsson/spotify-web-api-php/issues/234

Hey guys,

Question on the "createPlaylist" method.

Any reason why method using the following URI POST /v1/me/playlists instead of POST /v1/users/{userId}/playlists

Looking at the official documentation, the correct URI is POST /v1/users/{userId}/playlists
https://developer.spotify.com/documentation/web-api/reference/#endpoint-create-playlist

POST /v1/me/playlists is working fine, however, I worried that Spotify might drop it without warning and it will affect this library

Thanks

Originally created by @rac-andreharry on GitHub (Aug 23, 2021). Original GitHub issue: https://github.com/jwilsson/spotify-web-api-php/issues/234 Hey guys, Question on the "createPlaylist" method. Any reason why method using the following URI `POST /v1/me/playlists` instead of `POST /v1/users/{userId}/playlists` <img width="804" alt="Screenshot 2021-08-23 at 17 31 31" src="https://user-images.githubusercontent.com/56838396/130483852-7ea26e2a-dc89-49d2-9f33-239d7685fd0c.png"> Looking at the official documentation, the correct URI is `POST /v1/users/{userId}/playlists` https://developer.spotify.com/documentation/web-api/reference/#endpoint-create-playlist `POST /v1/me/playlists` is working fine, however, I worried that Spotify might drop it without warning and it will affect this library Thanks

kerem closed this issue

2026-02-27 19:26:24 +03:00

kerem commented

2026-02-27 19:26:25 +03:00

Author

Owner

@rac-andreharry commented on GitHub (Aug 23, 2021):

Actually nevermind, I found the reason
https://github.com/jwilsson/spotify-web-api-php/issues/131

@rac-andreharry commented on GitHub (Aug 23, 2021): Actually nevermind, I found the reason https://github.com/jwilsson/spotify-web-api-php/issues/131

kerem referenced this issue

2026-02-27 19:26:53 +03:00

[PR #166] [CLOSED] Added response filtering to improve UX #270