{"id":3026,"date":"2020-10-21T08:00:00","date_gmt":"2020-10-21T13:00:00","guid":{"rendered":"https:\/\/www.shipengine.com\/?p=3026"},"modified":"2020-10-21T08:00:00","modified_gmt":"2020-10-21T13:00:00","slug":"understanding-429-errors","status":"publish","type":"post","link":"https:\/\/www.shipstation.com\/blog\/understanding-429-errors\/","title":{"rendered":"Understanding 429 Errors & The Trick To Getting Around Rate Limits in ShipEngine"},"content":{"rendered":"\n

For an ecommerce business handling a high volume of shipments on a daily, or even hourly basis, repetitive 429 errors\u2014and the subsequent retries\u2014can become frustrating and wildly inefficient for fulfillment. So, in order to help, we have put together a guide to help users automate this retry process.

But, first let\u2019s better understand what a 429 Error is, and why it may occur in a ShipEngine API response. <\/p>\n\n\n\n

What Is a 429 Error? <\/strong><\/h2>\n\n\n\n

When using ShipEngine to perform actions and automations in your fulfillment workflow, you are making individual calls to our API, in which an HTTP client sends a request to an HTTP server, which then sends back a response containing the requested data, or \u201cresource\u201d.<\/p>\n\n\n\n

429 errors are generated when too many requests are made from the HTTP client<\/strong><\/a> to the server that hosts ShipEngine. Specifically, more than 100 API calls per minute will generate a 429 error in your response code. This mostly comes into play when a high-volume business creates GET posts for tracking events, since the API is often\u00a0

The solution?<\/p>\n\n\n\n

Enabling Rate Limits in ShipEnigne<\/strong><\/h2>\n\n\n\n

There are several reasons why rate limiting<\/a><\/strong> is beneficial:<\/p>\n\n\n\n