As I already posted to the growing thread of discontent at https://community.spotify.com/t5/Spotify-for-Developers/Changes-to-Web-API/m-p/6542355/highlight/true

As I already posted to the growing thread of discontent at https://community.spotify.com/t5/Spotify-for-Developers/Changes-to-Web-API/m-p/6542355/highlight/true#M15738 https://community.spotify.com/t5/Spotify-for-Developers/Chan... this is Spotify's usual deprecation strategy and they've done this before to their APIs. I think it's usually due to incompetence but this time that feels like only half the story. Sadly, despite their frequent self-sabotage, they still have the best API by a million miles. Anyway, anyone with a private project that doesn't mind a manual step, can grab an access token from https://open.spotify.com/get_access_token https://open.spotify.com/get_access_token using their browser. There's also projects like librespot (and various ports) which can provide access programmatically[0] using Spotify's client ID. Oauth is useless at preventing this kind of access. [0] https://github.com/librespot-org/librespot/wiki/Options#access-token https://github.com/librespot-org/librespot/wiki/Options#acce...).