The API implements a rate limiting system for all authenticated calls.
The purpose of this functionality is to protect servers from abuse and to provide a clear expectation of the level of service that
the API commits to fulfil.
Rate limits are defined across categories of API calls as described in the following table.
||Maximum allowed requests per second
||Maximum allowed requests per hour
|Market Data calls
Rate limit headers
The API communicates rate limit information in the headers of responses to all calls that are limited.
Specifically, the following headers are provided:
- X-RateLimit-Remaining – number of requests allowed against a the current limit
- X-RateLimit-Reset – time when the current limit will expire (Unix timestamp)
Sample rate limit headers
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Date: Fri, 18 Aug 2014 22:17:16 GMT
If one exceeds the above rate limits, then the API server will respond
with a rate limit error message with the HTTP status code 429 (Too
Many Requests) and the same rate limit headers one would receive in a normal response to limited call.