Try 30 days of free premium.

rate limit questions

geckoproj wrote a year ago: 1

Hi,

I had a few questions regarding the best practices when using your api.

I'm basically only calling the /episodes and /shows endpoints,

I read in the docs that for popular endpoints such as these the rate limit of 20 calls/10s could be avoided.

    - Does that mean that I can use the api while only worrying about handling the 429 response?

    - Or should I always add a delay between each call? if so how much would you suggest?

    - Is a +2sec wait increment for each consecutive 429 enough?

Thanks!


david wrote a year ago: 1

The rate limiting only takes place on the backend, not on the edge cache. This means if you request an endpoint that already has been requested by another user in the past hour, it will not count towards the rate limit. For endpoints like /shows and /episodes it's pretty likely that this is the case, but it's impossible to predict it fully.

If you want to be 100% sure that your request will succeed, wait 0.5 seconds between requests and you'll never hit the rate limit.

If you want to send requests as fast as possible, send them without delay until you hit a 429 response. When you do get a 429, back off either exponentially or with a static delay of e.g. 2 seconds.

geckoproj wrote a year ago: 1

Understood, thanks!!

Try 30 days of free premium.