Rate limiting

We use rate limiting to control the rate of requests to our applications. This way we protect and prevent our application from excessive use, whether its intended or unintended.

We monitor appropriate rate limits continuously and may adjust the limits based on the resources consumed. Rate limits can be different for different parts of the api and we strongly recommend that you write your code so that it uses these 3 response headers to determine when you can make the next call.

X-Rate-Limit-Limit
X-Rate-Limit-Remaining
X-Rate-Limit-Reset

X-Rate-Limit-Limit
This header tells you over how long time the rate limit windows is measured. If this value is '30s' it means that you can do calls in a 30 seconds time window.

X-Rate-Limit-Remaining:
The number of calls you have left to execute in the current time window based on 'X-Rate-Limit-Limit'

X-Rate-Limit-Reset:
When the current time window resets into a new one. Normally this would be the time for your first call plus 'X-Rate-Limit-Limit', but if you exceed the number of calls you're allowed to do, you might be locked out for a slightly longer amount of time. Therefor you should always take this value into account if your 'X-Rate-Limit-Remaining' number is 0 or below.