Deprecated API endpoints returns 404 with valid token
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I am aware of the recent API changes, but my application was put in extended mode well before this, so I have access to (now deprecated) endpoints. However, while I am quite sure I applied for all permission for said endpoints, I cannot check this any more, and right now, I am not able to access the following:
https://api.spotify.com/v1/recommendations?seed_artists=4NHQUGzhtTLFvgF5SZesLK&seed_genres=classical...
With a token, this returns a 404, not even a 403, and an empty body. This is the example on the API page.
https://api.spotify.com/v1/audio-analysis/11dFghVANM1KmJsNCbN1
With a token, this returns a 403 and sends a body containing: "{"error":{"status": 403}}"
I contacted support via the chat, and they referred me here. Can a dev or someone for whom this does still work contact me please?
All the best
- Labels:
-
API Access
-
API Bug
-
API Endpoint
-
API response
-
Web API
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page