429 Error: Too Many Requests After Accidental Infinite Loop

[vincent_20]

Hello,

I'm working on an application using Bubble that interacts with the Spotify API, specifically the "Create Playlist", "Get track", and "Add items to Playlist" endpoints. Due to an oversight in my workflow, I accidentally triggered an infinite loop that rapidly added a large number of items to a playlist (over 400+) in a short period.

Since this incident, I've been consistently receiving the HTTP 429 error, indicating "Too many requests." It's been approximately 6 hours since I first encountered this issue, and despite correcting the initial problem and adding waiting times between API actions, I am still facing the same error. I understand that there are rate limits in place to prevent abuse, but I'm uncertain about the duration of the block or if there's an issue with my access being flagged.

Can someone provide guidance on:

1. How long the "Too Many Requests" block typically lasts?
2. Is there a way to expedite the resolution or to check the status of my API access?
3. Any best practices to avoid such issues in the future?

I genuinely regret the oversight and have taken steps to ensure it doesn't happen again. I'd really appreciate any help or insight into resolving this issue and getting back to developing my application.

Thank you for your understanding and assistance!

[ZeBosse]

I am getting Error 429 (Too many requests) on a specific endpoint, too (in my case, get playlist name). Everything else worked fine two or so days ago... Also, I believe Spotify calculates rate limits based on a rolling 30-second period, so you should be fine there.

[vincent_20]

Hey thanks for your response.

Actually, I decided to delete my first app and make a new one. Not the most elegant solution, but this 429 error couldn't go...

It works fine now, I'll try not to make infinite loop again