[Closed] Scope Requirement Changed for Creating Private Playlists

[lplawlor]

My web app uses the Create Playlist endpoint to create a new private playlist:
https://developer.spotify.com/documentation/web-api/reference/create-playlist

In the past, this has only required the playlist-modify-private scope, but some time ago (in the last month or two), I began getting a 403 error from this endpoint (insufficient scope). Adding the playlist-modify-public scope fixes this.

Unfortunately, I now need to submit another extension request to get this new scope I previously didn't need. Not sure if this is a bug or not, but it could certainly be clearer in the API docs if not.


Edit: I've found the source of the bug, and it was fixable without changing the scope. Turns out, I was submitting my request with public: "false" rather than public: false. This used to work, but either a change was introduced to the Spotify API or to the JS libraries I am using that caused the string "false" to register as truth-y.