Rate limits

To ensure stability for all our API users and to encourage the development of an efficient integration, the following rate limits are in place:

• 600 requests per minute
• 20 requests per second

Each API response contains the following headers. They specify the rate limits set for your account and the remaining number of requests available for a given timeframe. Here's an example of the response headers of your first request:

"x-ratelimit-limit-minute": 600
"x-ratelimit-limit-second": 20
"x-ratelimit-remaining-minute": 599
"x-ratelimit-remaining-second": 19

When either the minute (x-ratelimit-limit-minute) or the second (x-ratelimit-limit-second) limit is reached, all the following API requests won't be processed and the HTTP response code 429 Too Many Requests will be returned until the limit has reset.

How to deal with rate limits

When developing your integration, keep the rate limits in mind so you can respond if they are hit. There are two main options:

• Check the value of the x-ratelimit-remaining-minute and x-ratelimit-remaining-second headers of each response before proceeding with the next request. If either one of the two values is equal to 1, pause any new requests until the time has elapsed and the limit is reset.
• If the rate limit is hit and the 429 Too Many Requests error is returned, pause any new requests until the time has elapsed and the limit is reset. Resume by reprocessing the last request that couldn't be processed