Avatar image for rick
#1 Posted by rick (506 posts) -

Many of you have noticed that our API rate limiting is stifling to put it mildly. We heard you and we, yet again, changed the way we limit API use. You'll like this one we're sure...


There's a limit of 450 requests within a 15 minute window. If you go above that you're temporarily blocked. You can make all those requests within anywhere from 1 second to 15 minutes.


TL;DR: Space out your requests so AT LEAST one second passes between each and you can make requests all day. Go even a millisecond faster and you'll hit a brick wall REALLY HARD.

There is no limit of the number of requests. You are limited to how often you can make requests. There are no hard numbers in this, its more of a throttling algorithm that will restrict aggressive apps and reward those that are well behaved. If your app spreads out requests to at most one per second you will not have any problems and can make requests 24/7. If the time between requests is less than 1 second you will be restricted and the more of these requests you make the more likely you will be blocked and proceeding amounts of allowed requests will dramatically drop.

Avatar image for conmused
#2 Posted by Conmused (47 posts) -

@edgework: Is this rate limiting based on endpoint, or the entire API? Just curious where to put my rate limiter.

Avatar image for conmused
#3 Posted by Conmused (47 posts) -

@edgework: Also, is this currently in effect? Even spacing out my requests, the giantbomb.com/api page seems to show me at ~200 requests an hour per endpoint, rather than an evenly paced 3600.

(I hit the api faster than 1 request/second at various points last night, when my rate limiter went haywire. So, that could explain it.)

Avatar image for rick
#4 Edited by rick (506 posts) -

@conmused: Not quite. Read this


Avatar image for conmused
#5 Posted by Conmused (47 posts) -