Getting 429 error(Too Many Request)

Chetan_123 — Thu, 22 Aug 2024 07:07:16 GMT

I’m a developer using your paid service and have subscribed for my app development. However, I’m consistently facing an issue with the following error:

Request failed with status code 429. Rate limit exceeded. Retry after 762 seconds.

I’m encountering this error specifically with these three endpoints:

Despite not sending multiple requests simultaneously, the error persists. All other endpoints are functioning correctly. My client is becoming frustrated—could you please resolve this issue as soon as possible?

Re: Getting 429 error(Too Many Request)

_brown — Sat, 19 Oct 2024 17:22:27 GMT

I'm encountering something similar for the /artists/{id}/albums endpoint. When I encounter a 429 response in general, my app will wait for the stated amount of time in the "Retry-After" header before making another request, and this typically works 99% of the time. However, sometimes when accessing the specific endpoint, I will suddenly get a 429 response with an extremely high "Retry-After" value (like 49000, or around 13.6 hours) despite the past few requests to other endpoints being successful with no 429 responses.

I understand if my app is continuing to make rapid requests and disregarding the rate limit then the "Retry-After" value would keep climbing, but this isn't the case for me. I am respecting the rate limit and "Retry-After" values, but it suddenly gives me a 429 response with a very high wait time seemingly out of nowhere, and only for the specific endpoint. When I refresh the app, other requests go through or have a normal "Retry-After" value, but on the first request to the specific endpoint it returns a 429 with a very high wait time.

A response from a Spotify staff or support member would be greatly appreciated.

topic Re: Getting 429 error(Too Many Request) in Spotify for Developers

Getting 429 error(Too Many Request)

Re: Getting 429 error(Too Many Request)