Error Codes

If an error occurs in API calling and no result is returned, identify the error cause based on the error codes of each API.

If an error occurs in API calling (for example, HTTP status code 400 or 505 is returned), the response body contains the specific error code and information.

If you are unable to identify the cause of an error, contact customer service and provide the error code so that we can help you solve the problem as soon as possible.

Error Response Body Format

If an error occurs during API calling, the system returns an error code and message to you. The following shows the format of an error response body:

{
    "error_msg": "Internal service exception",
    "error_code": "CB.00060101"
}

In the preceding information, error_code is an error code, and error_msg describes the error.

Error Code Description

If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to the instructions provided in API Gateway Error Codes.

Status Code	Error Code	Error Message	Description	Measure
500	CB.00060100	Network busy. Try again later.	Network busy. Try again later.	Try again later.
500	CB.00060101	Internal error.	Internal error.	Internal error.
400	CB.00060200	Invalid parameter.	Invalid parameter.	Check whether the parameter value is valid.
400	CB.00060201	Invalid task ID.	Invalid task ID.	Enter a valid task ID.
400	CB.00060202	Invalid service ID.	Invalid service ID.	The service ID can contain only lowercase letters and digits. Check whether the parameter is valid.
400	CB.00060203	Invalid file name.	Invalid file name.	The file name cannot be empty and cannot exceed 500 characters.
500	CB.00060211	Too many requests. Try again later.	Too many requests. Try again later.	Try again later.
400	CB.00060212	The file cannot be empty.	The file cannot be empty.	Check whether a file is selected for upload.
400	CB.00060213	You can upload a maximum of x files.	You can upload a maximum of x files.	Reduce the number of files to be uploaded at a time.
404	CB.00060214	URL not found.	Invalid URL.	Check whether the requested URL is correct.