Troubleshooting Centre
Shopify REST Admin API 429 and Retry-After: Managing Rate Limits
What a Shopify REST Admin API 429 response means, how to use the Retry-After header and how to design an integration job queue.
Shopify's REST Admin API calls may be throttled with a 429 Too Many Requests response in some circumstances. This page specifically covers existing or legacy integrations using the REST Admin API; Shopify recommends the GraphQL Admin API for new integrations.
What does Retry-After tell you?
According to Shopify's REST Admin API documentation, a 429 response when a limit is exceeded may include a Retry-After header. It specifies how long to wait before making another call. Many simultaneous retries can make the backlog worse.
What should you do?
- Track the endpoint, store and response code for each request.
- Respect the
Retry-Aftervalue if it is present in the API response. - Schedule jobs in a fair queue and consider separate traffic management for each store.
- Prevent retries from creating duplicate orders or records.
- Schedule large transfers outside peak periods and investigate more suitable API patterns.
A common architectural mistake
In an ERP–e-commerce integration, making frequent separate API calls for every SKU can create unnecessary load. Identifying records that need updates, grouping changes and using efficient methods supported by the resources can be more sustainable.
Prevention test
Users must not receive a false success message when a limit is exceeded. Show the operations team the queue delay, last successful sync and number of pending jobs.
How should you read the example response?
The illustrative response below shows that this store and application have reached their request limit. Do not schedule another attempt before the waiting period ends; account for other jobs working with the same store in the meantime.
HTTP 429 Too Many Requests
Retry-After: 2.0
X-Shopify-Shop-Api-Call-Limit: 40/40
These figures are examples, not fixed quotas for every store plan. Shopify rate limit documentation.
| Situation | Recommended approach |
|---|---|
| Valid Retry-After | Do not retry before the specified interval has elapsed |
| Missing or malformed header | Use your own bounded waiting policy and investigate the cause |
| Persistent 429 responses | Reduce load and transfer scope; stop when the retry budget is exhausted |
New projects should evaluate the current GraphQL Admin API approach instead of REST; its cost and query limits differ from REST's request-count model. This guide should not be used to resolve GraphQL errors.
When should an administrator help?
If the issue persists despite respecting Retry-After and application or store limits, review all workers and queues using that store together. Share a sanitised request ID, time and limit headers with product support; do not share the access token. Reconcile already accepted records before processing pending writes.
Sources and verification
Example flows are architectural recommendations, not claims of completed client projects or vendor partnerships. Technical sources checked: 17 October 2026. Installation version, licence and permissions must be verified separately.
Adapt it to your business workflow
ERP integration planning guide. Explore the scope of custom software development for further reading; we can assess your current process together.
Let's discuss your needs →