Note: If you receive an error for too many requests, please wait for at least 5 minutes before trying a corrected request. Retrying more frequently will cause repeated failures due to cache timing.
429 - Too Many Requests
A 429 status code is returned when request counts exceed a throttle limit.
Every request can be subjected to two different throttles: those where an integration is sending requests at a rate above the limit and those where the EPS servers are experiencing load above the limit.
When a partner makes an EPS API request, the receiving server checks if the request count is within the limit. If the request count is within the limit, the request goes through and the count is increased for the client.
If the client request count exceeds the limit, the server will return a response with an HTTP 429 (Too Many Requests) status code.
The server can optionally include a `Rate-Limit-Day-Reset`& 'Rate-Limit-Minute-Reset' header. This indicates how long you should wait before sending your next request. They are the timestamps when the next tumble will occur, in microseconds (not milliseconds).
For example, when converted to a date/time, the value '15489792000000' results in `Friday, February 1, 2019 12:00:00 AM` (UTC).
HTTP/1.1 429 Too Many Requests
Date →Fri, 01 Feb 2019 06:20:51 GMT