Spotify Web API
GET /v1/audio-analysis/{id} stops working on new apps
Stopped workingSubscribe to Spotify Web APIShare
On November 27, 2024, Spotify Web API removed access to the GET /v1/audio-analysis/{id} endpoint for new apps. Requests to this endpoint from newly created applications now fail. Applications created before this change that already have extended mode access keep their access.
Calls it hits
GET /v1/audio-analysis/{id}
What to use instead of these calls
Spotify offers no replacement for this endpoint. Apps with existing extended mode access can continue using it.
In Spotify Web API's words
Effective today, new Web API use cases will no longer be able to access or use the following endpoints and functionality in their third-party applications.
Facts
- API
- Spotify Web API
api.spotify.com - Kind
- Removal
- Announced
- November 27, 2024
- Takes effect
- November 27, 2024
- Calls after that day
- Fail
- Who it affects
- new apps
- Source
- Announcement
- Last updated
- Verified
- , against Spotify Web API's own pages
Questions
When does this change take effect?
Calls to GET /v1/audio-analysis/{id} on Spotify Web API stopped working on November 27, 2024.
What happens to calls after November 27, 2024?
They have failed since November 27, 2024.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Spotify Web API 5
-
GET /v1/audio-features*Removal Stopped working -
GET /v1/artists/{id}/related-artistsRemoval Stopped working -
GET /v1/recommendationsRemoval Stopped working -
/v1/playlists/{id}/tracksRemoval Stopped working -
GET /v1/tracksRemoval Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.