To ensure that our products perform at consistently high service levels, we set both a rate limit and a timeout value.

It is unlikely you will breach the rate limiting threshold, but if you do, then calls from any of your tokens will return an HTTP status code of 429 - Too Many Requests until the window resets and you can submit requests successfully once again.

To help prevent yourself from hitting these limits and to understand HTTP 429 - Too Many Requests further, the API returns headers which detail your current rate limit status.

Header Description Example
X-Rate-Limit-Limit The maximum number of requests a customer is allowed to make per minute. 150
X-Rate-Limit-Remaining The number of requests you have remaining in the current rate limit window. 5
X-Rate-Limit-Reset The time at which the current rate limit window resets. Expressed in UTC epoch seconds. 1547453281