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...
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.
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.
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?
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…