Rate limits

The API operates rate limits based on the account associated to the token. Every API response header contains the following headers:

X-Ratelimit-Limit: 10/2

The rate limit calculation info. the above example means “10 requests per 2 seconds”.

X-Ratelimit-Remaining: 7

The number of remaning call available. The refresh rate depends on time window defined in X-Ratelimit-Limit header. With the example above, 7 call are available until the next window. The bucket is refreshed every 2 seconds, so 10 new request will be available.


Once the limit is reached, the API returns a Too Many Request (429) response, with a pessimistic evaluation time to wait before the next allowed request. This value is expressed in seconds, in the X-RateLimit-Wait header.

HTTP/1.1 429 Too Many Requests
Content-Type: application/problem+json
X-RateLimit-Wait: 0.5

{
    "type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html",
    "title":"Too Many Requests",
    "detail":"Rate limit exceeded",
    "status":429
}

As this area can be subject to changes, we highly recommend you to programatically implements a wait and retry strategy based on those headers information.