Http status code
SHOPLINE API response Status Code and Error Description
When SHOPLINE receives requests for API, is can response with different HTTP status code based on original request
| Status Code | Result | Description |
|---|---|---|
| 200 | ok | Request has been processed successfully |
| 201 | Created | Request is completed and new resource has been created |
| 202 | Accepted | the request has been accepted for processing but not completed |
| 303 | See Other | the resource you requested is located at another URI (address) by using the GET HTTP method |
| 400 | Bad Request | Server fails to process the request, normally because of syntax error, or the header or Content-Type is not set as application/json, or incorrect parameter type of request |
| 401 | Unauthorized | Authentication error, including two possible scenarios: 1. Access token not provided. 2. Access token provided, but incorrect or expired. If the access token is incorrect, request the merchant to reauthorize the app. If the access token is expired, request the merchant to reauthorize the app or use the refreshToken API to obtain a new access token |
| 402 | Payment Required | Requested store has been frozen, store owner needs to log in to store Admin and clear the outstanding balance to unfreeze the store |
| 403 | Forbidden | Server refuses to response to the request |
| 404 | Not Found | Can not find your requested resource |
| 406 | Not Acceptable | Request header of Accept includes unacceptable type |
| 412 | Precondition Failed | Precondition Failed，The request body contains high-risk content |
| 422 | Unprocessable Entity | Format of request body is correct, but there is still the semantic error, Error 422 includes but not limited to: |
| 423 | Locked | Requested store is locked now,For example exceeds the limit of API requests, or there are some problems with the account, such as fraud and leakage risks are detected, and the store is locked.If your store is locked, please contact SHOPLINE. |
| 429 | Too Many Requests | Requests are restricted, as frequency limit for accessing the interface of program has been exceeded |
| 433 | Request Blocked | The request was blocked because it was identified as a malicious request, or the IP address was added to a blacklist. A malicious request is required to wait for a certain time before it can continue to access the service. |
| 434 | Excessive Rate Limit Surpassed | The request rate far exceeds the allowed limit. |
| 435 | Challenge Collapsar Attack | The request was identified as a Challenge Collapsar (CC) attack. |
| 436 | Security Policy Triggered | The request content triggered SHOPLINE's security policy. |
| 500 | Internal Server Error | SHOPLINE internal error，If you encountered this problem, please contact SHOPLINE. |
| 501 | Not Implemented | Requested interface is not available in that special store, such as external App has requested a SHOPLINE interface only available for internal Apps, this could also mean that the interface is prepared for future use. |
| 503 | Service Unavailable | Server is unavailable now |
| 504 | Gateway Timeout | Failed to response in time and caused timeout Please try to divide your request into some smaller requests |
Was this article helpful to you?
