API call limit
The Shopify platform applies call limits to the requests that it receives. Most requests are throttled generally based on a leaky bucket algorithm. But some requests, such as those for creating product variants, can have specific limits depending on your store's data.
Calculating API call limits with the leaky bucket algorithm
The API call limit operates using a leaky bucket algorithm as a controller. This allows for infrequent bursts of calls, and allows your app to continue to make an unlimited amount of calls over time. The bucket size is 40 calls, and this can't be exceeded at any given time or a 429 bucket overflow error is returned. The bucket empties at a leak rate of two calls per second, which means that apps averaging two calls per second avoid bucket errors. Learn more about the leaky bucket algorithm.
Your API calls are processed almost instantly if there is room in your bucket. Unlike some integrations of the leaky bucket algorithm that aim to smooth out operations, you can make quick bursts of API calls that exceed the leak rate. The bucket analogy is still a limit that Shopify tracks, but your processing speed for API calls is not directly limited to the leak rate of two calls per second.
Staying within API call limits
If your app exceeds the 40-call bucket size (or if you cross a request limit that's specific to a resource), then a
429 Too Many Requests error is returned.
Designing your app with API call limits in mind is the best way to avoid these errors. For example, you can stagger API requests in a queue and do other processing tasks while waiting for the next queued job to run.
To avoid call limit errors, keep the following in mind:
You can check how many calls you've already made using the Shopify header that was sent in response to your API call.
HTTP_X_SHOPIFY_SHOP_API_CALL_LIMITlists how many calls you've made for that particular shop:
X decreases over time. If you see you're at 39/40 calls, and wait ten seconds, you'll be down to 19/40 calls.
In general, you can retrieve a maximum of 250 objects with one API call.
You can update only one API resource with one API call.
Creating an example throttling program
This example throttling program pauses and resumes during data processing and does not exceed the API call limit. The program connects to a Shopify store, reads the products, and deletes any products that are out of stock.
To run the example program:
In your code editor of choice, create a new Ruby file called
Add the code below and provide your API key, API password, and myshopify sub-domain in the relevant placeholders:
- Add the engine code. This code fetches all products and deletes the ones that are not available:
- Open a Ruby console or launch Terminal.
- Browse to your program and run it:
API call limits for specific endpoints
The following endpoints have additional throttles that can be applied for different reasons based on your shop or client data.
If an app reaches an API call limit for a specific resource, then it receives a
429 Too Many Requests response, and a message that a throttle has been applied. The response also describes the limit that's been reached. When your app receives one of these responses, it should implement retry behavior (such as an exponential backoff algorithm) to complete the call at a later time.