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 noticed, that I get always an error on the audio-analysis endpoint for specific spotify ids.
Error happens e.g. for "0czhnkeYm4fzpcaeIVjMJu"
but everything works fine for example on "6L6HX2RwtQe2JbmxX3DzvD".
This seams a bit different from the plain 429 error due to rate limits.
With Spotipy I get also get a ResponseError('too many 502 error responses') notice, but it is handled similar and forwarded as a 429 error. In fact it seems that it can can cause future 429 errors on other requests if your code reties too often to request the analysis and you hit the rate limit.
Has anybody made a similar experience? Is there some fix by Spotify?
Best regards