Search rate limits

[mebibite]

I've been writing a program that, among other things, searches for songs, and could make upwards of a few hundred search requests in one run (this is unavoidable, there is no way to lessen the amount of requests other than setting a hard upper limit in the program for how many songs to request). I've spaced them out with reasonable wait times (at least 1s between each request), but I'm still hitting what seems to be overall rate limits (not 30-second rolling rate limits like described in the API documentation), that cause 24-hour lockouts. So what are the numbers for this rate limit? How can I find what the rate limit is so I can set a hard limit in my program? It would be extremely helpful to have a solid upper limit so I don't have to keep guessing and then getting locked out for 24 hours at a time.

[aderpynarwhal]

From my own trial and error over the last year, I always tapped out around 5k. You can see your daily rate usage on your developer dashboard under metrics. I'm not sure if they lowered the upper limit after the nuke in february but it's possible it could be lower.

[mebibite]

That's strange - after quite a while of testing it seems my limit is exactly 700, maybe per 24 hours? Which is very frustrating, to be honest, since for various reasons 1000 was what I would've wanted as the upper limit even if the theoretical limit was higher. It's also strange that it works completely differently to how the rate limits are documented, since the docs only say there's a rolling 30-second rate limit when this is obviously a longer-term limit.