430 HTTP Status Code
HTTP response status code 430 is an unofficial client error specific to Shopify and is returned by the server to indicate that too many HTTP requests are being made using the API within a certain period.
Usage
When the 430 status code is received, the server is refusing to process the HTTP request because too many HTTP requests are made to the API in too close a succession. This error has been reported during web crawling events, such as when a store operator is testing their site. It can be avoided and solved by increasing the limit on the maximum number of HTTP requests over a given time.
This is similar to the HTTP Response status code 429 Too Many Requests, which is an official status that is relevant and applicable in such cases.
Note
In the IETF draft specification, HTTP response 430 was originally reserved for Request Header Fields Too Large. However, that has been changed to status 431. Also, in another IETF draft, there is mention of a 430 Would Block status that was to be implemented to address the problem of head-of-line blocking in HTTP/1.1 pipelining. However, with the introduction of HTTP/2, the problem was solved and the 430 Would Block status code was never finalized.
Note
The status code 430 Too many API calls is deprecated and no longer appears in the Shopify API response status and error codes.
Note
Search engines like Google will not index a URL with 430 response status, and consequently, URLs that have been indexed in the past but are now returning this HTTP status code will be removed from the search results.
Takeaway
The 430 status code is a client error that is specific to Shopify and indicates that the server is unwilling to process the HTTP request because too many API HTTP requests have been made, too close together. A better alternative to use is 429 Too Many Requests.