All API queries return HTTP status codes that contain more information about the response.
GraphQL HTTP status codes are different from REST API status codes. Most importantly, the GraphQL API can return a 200 OK response code in cases that would typically produce 4xx or 5xx errors in REST.
The response for the errors object contains additional detail to help you debug your operation.
The response for mutations contains additional detail to help debug your query. To access this, you must request userErrors.
A list of all errors returned
Contains details about the error(s).
Provides more information about the error(s) including properties and metadata.
Shows error codes common to Shopify. Additional error codes may also be shown.
The client has exceeded the rate limit. Similar to 429 Too Many Requests.
The client doesn’t have correct authentication credentials. Similar to 401 Unauthorized.
The shop is not active. This can happen when stores repeatedly exceed API rate limits or due to fraud risk.
Shopify experienced an internal error while processing the request. This error is returned instead of 500 Internal Server Error in most circumstances.
{ "errors": [ { "message": "Query cost is 2003, which exceeds the single query max cost limit (1000). See https://shopify.dev/concepts/about-apis/rate-limits for more information on how the cost of a query is calculated. To query larger amounts of data with fewer limits, bulk operations should be used instead. See https://shopify.dev/tutorials/perform-bulk-operations-with-admin-api for usage details. ", "extensions": { "code": "MAX_COST_EXCEEDED", "cost": 2003, "maxCost": 1000, "documentation": "https://shopify.dev/api/usage/rate-limits" } } ] }{ "errors": [ { "message": "Internal error. Looks like something went wrong on our end. Request ID: 1b355a21-7117-44c5-8d8b-8948082f40a8 (include this in support requests).", "extensions": { "code": "INTERNAL_SERVER_ERROR", "requestId": "1b355a21-7117-44c5-8d8b-8948082f40a8" } } ] }
The 4xx and 5xx errors occur infrequently. They are often related to network communications, your account, or an issue with Shopify’s services.
Many errors that would typically return a 4xx or 5xx status code, return an HTTP 200 errors response instead. Refer to the 200 OK section above for details.
The server will not process the request.
The shop is frozen. The shop owner will need to pay the outstanding balance to unfreeze the shop.
The shop is forbidden. Returned if the store has been marked as fraudulent.
The resource isn’t available. This is often caused by querying for something that’s been deleted.
The shop isn’t available. This can happen when stores repeatedly exceed API rate limits or due to fraud risk.
An internal error occurred in Shopify. Check out the Shopify status page for more information.
HTTP/1.1 400 Bad Request { "errors": { "query": "Required parameter missing or invalid" } }HTTP/1.1 402 Payment Required { "errors": "This shop's plan does not have access to this feature" }HTTP/1.1 403 Forbidden { "errors": "Unavailable Shop" }HTTP/1.1 404 Not Found { "errors": "Not Found" }HTTP/1.1 423 Locked { "errors": "This shop is unavailable" }HTTP/1.1 500 Internal Server Error { "errors": "An unexpected error occurred" }
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3