topic Previously working code now triggers 429 errors without any changes. in Spotify for Developers

Previously working code now triggers 429 errors without any changes.

stefanobras — Mon, 11 Mar 2024 18:26:26 GMT

I'm currently developing an app locally that creates a playlist using some JS logic and by fetching data from the API:

-Getting All Artists from a certain Genre.
-Getting All Albums from a certain Artist.
-Getting All Track from a certain Album.

Everything used to work just fine and I was able to successfully create a few playlists with my own user. I authorize, start the logic and when its done the playlist is created in my profile.

However, suddenly I've been getting 429 too many requests errors when I try to fetch "All Albums from a certain Artist." when this didn't use to happen before and nothing in my code has changed. Is it possible that I've been temporarily blocked by the API for suspicious activity or something?

My app is called Music Time Traveler and the id for it seems to be 382ee2428fd44ee387e279e5dcee5cf9

Re: Previously working code now triggers 429 errors without any changes.

stefanobras — Mon, 11 Mar 2024 15:01:08 GMT

Access to XMLHttpRequest at 'https://accounts.spotify.com/api/token' from origin 'XXX' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Everything seemed to start with this, that's why I'm asking if perhaps I've been blocked.

Re: Previously working code now triggers 429 errors without any changes.

stefanobras — Tue, 12 Mar 2024 20:17:26 GMT

Waited a day and the 429 errors magically disappeared... Spotify should really just tell us the truth and explain the daily limits of requests instead of flat out lie and give errors that are misleading, my code was fine and wasn't requesting too much.