# Appendix 1:Global Error Codes
# Description
Each time the interface is called, a code may be returned. Based on the return, you can debug the interface and troubleshoot errors.
Notes.
- You are supposed to troubleshoot by codes instead of error messages as they may be adjusted.
- If the request parameters do not conform to the json specification, this may result in the CJ server parsing the parameters incompletely, in which the interface will return "The request parameter is not in a correct JSON format". You need to check the request parameters of json.
# Error Code Description
Return Code | Error Description | Troubleshooting |
---|---|---|
200 | Success | Success |
1600000 | System busy, please contact CJ IT | System busy, please contact CJ IT |
1600001 | Invalid API key or access token. How to get access token: https://developers.cjdropshipping.cn/en/api/api2/api/auth.html#_1-1-get-access-token-post | Get new access token, View Docs |
1600002 | access token cannot be empty | Access token cannot be empty, Please input the correct token |
1600003 | Invalid Refresh token | Use the correct Refresh token or Get new access token, View Docs |
1600031 | Invalid platform token | Invalid platform token, Get new platform access token, View Docs |
1600030 | token invalidation fail | token invalidation fail, Get new access token, View Docs |
1600004 | Authorization failed, Please check cj account | Please check if your email and API key are correct, or if your API store is Authorized |
1600005 | Email or password wrong, please check and try again | Please check if your email and API key are correct, or if your API store is Authorized |
1600006 | Developer account not found | Please check if your email and API key are correct, or if your API store is Authorized |
1600007 | The user has been bound to another developer account | The user has been bound to another developer account |
1600008 | Authorization failed, Please check cj account | Please check if your email and API key are correct, or if your API store is Authorized |
1600009 | Token exchange failed because the code does not exist. | Token exchange failed because the code does not exist. |
1600010 | RedirectUri must be not empty. | RedirectUri must be not empty. |
1600011 | CallbackUri must be not empty. | CallbackUri must be not empty. |
1600012 | The account creation authorization has been disabled, and cj authorization cannot be created. Contact the CJ account manager. | The account creation authorization has been disabled, and cj authorization cannot be created. Contact the CJ account manager. |
1600013 | Store info does not exist,please check and try again. | Store info does not exist,please check and try again. |
1600100 | Interface is offline | Interface is offline |
1600101 | Interface not found | Interface not found |
1600200 | Too much request{param} | Regulate the rate of your requests for smoother distribution. Refer to: Access Frequency Restrictions |
1600201 | Quota has been used up | Regulate the rate of your requests for smoother distribution. Refer to: Access Frequency Restrictions |
1600300 | Param error | Check your parameters and enter correct value. |
1600301 | Read timed out | Read timed out, Wait a moment and try again |
1601000 | User not found | Please check if your email and API key are correct, or if your API store is Authorized |
1602000 | Variant not found | Variant not found |
1602001 | Product not found | Product not found |
1602002 | Product has been removed from shelves | Order confirm fail, Please contact CJ Agent |
1602003 | Variant has been removed from shelves | Variant has been removed from shelves |
1602004 | Failed to create infringement report | Failed to create infringement report |
1603000 | Order create fail | Order create fail |
1603001 | Order confirm fail | Order confirm fail |
1603002 | Order delete fail | Order delete fail |
1603003 | Order exist, please do not duplicate create | Order exist, please do not duplicate create |
1603100 | Order not found, please check the CJ order id | Order not found, please check the CJ order id |
1603101 | Order pay fail, please contact CJ order center | Order pay fail, please contact CJ Agent |
1603102 | Inventory deduction fail, please contact CJ order center | Inventory deduction fail, please contact CJ Agent |
1604000 | Balance is insufficient | Balance is insufficient |
1604001 | The balance payment function is temporarily restricted. Please log in to My CJ and make the order payment on the page | please contact CJ Agent |
1605000 | Logistic not found | Logistic not found |
1605001 | Logistic invalid, please reference freight calculate. | Logistic invalid, please reference freight calculate. |
1605002 | country code not found | country code not found |
1606000 | Webhook setting add fail, Webhook already have settings | Webhook setting add fail, Webhook already have settings |
1606001 | Webhook set fail | Webhook set fail |
1607000 | Webhook url error | Webhook url error |
1607000 | Webhook url error, Please ensure URL starts with https:// | Webhook url error, Please ensure URL starts with https:// |
1607001 | Please do not use domain names such as ngrok | Please do not use domain names such as ngrok |
1607003 | Webhook url error, Http Status must be 200 | Webhook url error, Http Status must be 200 |
16070002 | The CJ page type is not supported | The CJ page type is not supported |
1607004 | Freight calculation request failed | Freight calculation request failed |
1607006 | Query dispute product request failed | Query dispute product request failed |
1607007 | dispute confirm fail | dispute confirm fail |
1607008 | dispute create fail | dispute create fail |
1607009 | dispute cancel fail | dispute cancel fail |
1607010 | product update fail | product update fail |
16900202 | Request method '{param}' not supported | Please check the API documentation to confirm which HTTP method is required for this request, update it and retry. |
16900203 | Content type not supported[{param}] | Please check the API documentation to confirm which Content-Type is required for this request, update it and retry. |
16900204 | Required request body is missing | Check the API documentation and add request body. |
16900205 | The request parameter is not in a correct JSON format | Check the API documentation use the correct JSON data |
16900403 | {param} can not be emptry | Check your parameters and enter correct value. |
# Troubleshooting methods
# Error code: 1600200
Interface call exceeds limit.
- For specific frequency policy, Refer to: Access Frequency Restrictions
- The time is the same. For example, if you beyond the minutes limits, you can request again after minutes, while it will be hours if you beyond the hours limits.
- Our rate limit is not strict. For the calls, the following optimizations are considered.
- When the interface is implemented, only system failures need call again. For other error codes, the specific failure shall figured out.
- The call is reasonable or not. For a real-time synchronization, it can be changed to a timed task call as too many calls of one user will cause a bad experience.
# Error code: 1600300
Invalid Parameter. It doesn't meet the system requirements. You can refer to the specific API interface instruction. Also, you need to confirm:
- It is a correct Http request method. For example, if the interface requires the Post method, you cannot use the Get method.
- It is a correct Http request parameter. For example, if the interface requires a json structure, it cannot be passed as an url parameter or form-data.