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...
Im currently developing a web application utilizing the spotify web api. At first I didnt completely read through the documentation and soon encountered 429 errors. As I didn't have any mechanisms implemented to prevent my application from requesting after a 429 error, my application made a bunch of requests which skyrocketed the amount of time my rate limit was applied. (like almost 48 hours). So I used the time to change my app to take the rate limit into account. Now it blocks requests to the url after the first 429 error for the amount provided in the 'Retry-After'.
So after these 48 hours I tested it and made a bunch of requests, which resulted in a 429 response. My application stopped as soon as the first 429 response was received. But the value of the Retry-After header is about 21 HOURS. So is there a way to detect the rate limit before a 429 response is provided? Or will my application just be locked for 21 HOURS everytime I violate the rate limit for ONE SINGLE TIME?