Why am I getting 429 Too Many Requests errors when trying to access the API?

A 429 status code is returned when request counts exceed a throttle limit.

What do I need to do?

If you receive a 429 status code error, you have either exceeded your account's throttle limit or EAN servers are experiencing a high load. Take note of any Retry-After value included in the response header and wait this length of time before sending your next request.

How does EAN throttle requests?

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 EAN servers are experiencing load above the limit.

When a partner makes an EAN 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 partner.

If the partner request count exceeds the limit, the server will return a response with a HTTP 429 (Too Many Requests) status code.

The server can optionally include a `Retry-After` header. This indicates how long you should wait before sending your next request.

Example:

HTTP/1.1 429 Too Many Requests
Content-Type: text/html
Retry-After: 30
Was this article helpful?
2 out of 2 found this helpful
Have more questions? Submit a request

Comments