Hacker News Reader

I’m serving everything from the Spotify API directly on Noiseblend (https://noiseblend.com) and rate limit has never been a problem.

When a request fails because of a rate limit, Spotify responds with 429 and a Retry-After header so you know when to schedule the next request.

In my tests, that header never had a value greater than 10 seconds, and 429 responses were very rare.

View on HN

Right, but you are using user login, and I think that gives you a lot more rate than a single account doing all the requests, which is what you need to get the no-sign-in experience on songdata.io - right?

Indeed, I forgot about that part...

I think all of my requests to Spotify have been done on behalf of authenticated users. But I guess you could authenticate with your own user to lift up the limits.

Spotify rate limits are per app, not per user.

Reply on news.ycombinator.com