Shoplazza API response status and error codes
The following table provides an overview of common HTTP status codes and their meanings when interacting with the Shoplazza API:
Status Code | Details |
|---|---|
200 OK | The request was successfully processed by Shoplazza. |
400 Bad Request | The request wasn't understood by the server, generally due to bad syntax or because the |
401 Unauthorized | The necessary authentication credentials are not present in the request or are incorrect. |
403 Forbidden | The server is refusing to respond to the request. This status is generally returned if the application hasn't requested the appropriate scope for the action. |
404 Not Found | The requested resource was not found. |
405 Method Not Allowed | The server recognizes the request but rejects the specific HTTP method. |
406 Not Acceptable | the server cannot produce a response that matches the client's request, e.g. refund an order which is not in after-sale status. |
422 Unprocessable Entity | The request parameters are formatted incorrectly. Common causes for this error include: |
429 Too Many Requests | The request was not accepted because the application has exceeded the API rate limit. Adjust request frequency. Learn more about Shoplazza's API rate limits. |
500 Internal Server Error | An internal error occurred in Shoplazza. Simplify or retry your request. If the issue persists, record any error codes and timestamps and contact Partner Support for assistance. |
