Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
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