Rate Limits

By enforcing request rate limits, we try to fairly and evenly distribute our capacity amongst our merchants and prevent apps from abusing these resources.

Response Headers

The following indicates a set of three headers which might be returned with a response to a call to any of the API endpoints.

X-RateLimit-Remaining: 1959
X-RateLimit-Limit: 2000
X-RateLimit-Reset: 300

The first header, X-RateLimit-Remaining, shows total requests remaining for this cycle (1959). X-RateLimit-Limit displays the total capacity (2000). X-RateLimit-Reset Number of seconds until the remaining number of requests will be reset to the capacity; in this case, X-RateLimit-Remaining will be reset to 2000 requests in 300 seconds.

Exceeding Limits

Exceeding any rate limits, will return status code 429 (Too many requests). The Retry-After header will contain the number of seconds before another request of this type can be made – if your request receives a 429 code (Too many requests), your application should wait until the Retry-After period has elapsed before attempting the same kind of request.

This section was last updated on May 19, 2014 and replaces all previous versions of this document.