-
Notifications
You must be signed in to change notification settings - Fork 959
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sudden breaking API changes - Depreciated endpoints #1172
Comments
Of course on the day I finish something that makes use of their audio analysis 💀 |
This is the worst. They also made it impossible to retrieve data from playlists like Release Radar or New Music Friday, which I was using on weekly basis. |
I ran into the same problem with my personal script I used every week to get data from Release Radar. A workaround for that is copying these playlists using the Spotify app (mobile or desktop) and using that playlist to retrieve data from it. |
I think Spotify is trying to keep the data they generate on their site. But this breaks more "normal" applications than malicious ones. |
Is there anyway I can get access to a songs metadata now that they have deprecated the API endpoint |
Even the recommendation endpoint was removed.... wow |
Describe the bug
Spotify have made sudden breaking changes to their API, depreciating many endpoints (making them unavailable to many current users)
https://developer.spotify.com/blog/2024-11-27-changes-to-the-web-api
Additional context
Spotipy documentation might need to be updated to reflect this depreciation.
The text was updated successfully, but these errors were encountered: