Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Getting error 429 only when requesting audio features from a track

Getting error 429 only when requesting audio features from a track

I'm basically working with the API for a data mining university project.
I'm getting error 429 on a piece of code that extracts the audio features from some tracks. Can't perform a single request, the first one gets automatically blocked.

The thing is that I don't get 429 when running another piece of code that uses the same exact client id / secret token (this one extracts all the tracks from some playlists).

 

It looks like I'm just blocked from performing audio feature requests.

Reply
8 Replies

I've got the same problem. Actually seemed to work fine yesterday night (in batches of 100) but now today it fails for even a single request. As OP said, other requests (fetching user library songs in batches of 50 for instance) still work fine, with the same id/secret token pair. It's driving me nuts.

I eventually got around the problem by using other machines (in this case it was a matter of time until I was blocked on those too) and by using google colab to run my code for a few days, which is not optimal for every case but for my project it worked just fine as I never got blocked there

I've read recently that someone solved it by rotating their client secret.

XimzendSpotify Star
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Note: I'm not a Spotify employee.

Didn't work for me at the time

A 429 status code indicates that your app has been rate-limited. See this article for more information.

 

Rate-limiting applies on a per-client id basis (as opposed to, for example, a per-Spotify user basis). This explains why rotating your client id will increase your effective rate limit.

Having the same problem and looking for any clarity, resetting the client secret doesn't seem to be working. Will the audio feature rate limit for these creds reset after a certain amount of time or are they cooked?

Any solution? I have the same problem where my code was running just fine until it suddenly kept getting 429 errors in the same random line of fetching small amounts of data and it just seems like I've been blocked or something.

Hey did you ever figure it out?

Suggested posts