Historical Error Codes

Updated on 2025-02-10 GMT+08:00

View PDF

If an error occurs during API calling, no result is returned. You can locate the cause of an error using the error codes of each API. If an error occurs in API calling, HTTP status code 4xx or 5xx is returned. The returned message body contains a specific error code and error message. 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.

Format of an Error Response Body

If an error occurs during API calling, an error code and a message will be displayed. The following shows an error response body.

{
    "error_code": "OSM.0001",
    "error_msg": "failed"
}

In the error response body, error_code is an error code, and error_msg provides information about 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	Solution
400	OSM.0001	Failed	Exception occurs when verifying parameters.	Check the parameters.
401	OSM.0002	Unauthorized	Authentication failed.	Check whether the token has expired or obtain a new token.
403	OSM.0003	Forbidden	Illegal operation.	Illegal operation.
500	OSM.0004	Internal Server Error	Internal error.	Contact technical support engineers.
200	OSM.01010001	Param validation failed.	Failed to verify the parameters.	Check the parameters by referring to the API document.
200	OSM.01010002	No operation permission.	No operation permission.	No operation permission.
200	OSM.01010003	Account and password not matched.	Incorrect account or password.	Check the account or password.
200	OSM.01010004	You have asked for the order, please ask for it later.	Urging is too frequent. Please try again later.	Urging is too frequent. Please try again later.
200	OSM.01010005	Upload accessory size exceeded limit today.	The total size of files to be uploaded on a day exceeds the upper limit.	The total size of files to be uploaded on a day exceeds the upper limit.
200	OSM.01010006	Severity Id not exists.	Severity ID does not exist.	Severity ID does not exist.
200	OSM.01010007	This tenant has no role to create a case.	Tenant has no role information.	Refer to the error message, or contact technical support engineers.
200	OSM.01010008	Carbon copy email not valid.	Invalid CC email address.	Invalid CC email address. Check its length and format.
200	OSM.01010009	Can't create case because of customer benefit not match rule.	Failed to create the service ticket because the support plan benefits do not match.	Check the current support plan benefits and see whether fault reporting service tickets can be created.
200	OSM.01010010	Verify not pass.	Verification failed.	Refer to the error message, or contact support engineers.
200	OSM.01010011	Can't get customer info from token.	Cannot obtain customer information from the token.	Refer to the error message, or contact technical engineers.
200	OSM.01010012	The type must be 0 or 1.	Type must be 0 or 1.	Type must be 0 or 1.
200	OSM.01010013	The operation must be cancel or close or press or delete.	Operation type must be cancel, close, urge, or delete.	Operation type must be cancel, close, urge, or delete.
200	OSM.01010014	Operation failed.	Internal error.	Contact technical support engineers.
200	OSM.01010015	This case does not exist.	Service ticket does not exist.	Check the service ticket ID, or contact technical support engineers.
200	OSM.01010016	The createFeedbacktypeReq's feedbackCreateInfos cannot be empty.	The request for creating feedback type cannot be empty.	Refer to the error description, or contact technical support engineers.
200	OSM.01010017	Operation failed.	Internal service error.	Contact technical support engineers.
200	OSM.01010018	Auth operate type not support.	Operation is not supported.	Refer to the error message, or contact technical support engineers.
200	OSM.01010019	The operation is illegal.	Illegal operation.	Refer to the error description, or contact technical support engineers.
200	OSM.01010020	The customerId does not exist.	Customer ID does not exist.	View the customer ID.
200	OSM.01010021	Cbh operation failed.	Bastion host exception.	Contact technical support engineers.
200	OSM.01010022	The case has just been created, please press the case later.	The service ticket was just created. Please urge later.	Refer to the error message.
200	OSM.01010024	Verification code resent too frequently.	Verification code requested too frequently.	A verification code is valid for 5 minutes and is sent within 1 minute. Please wait or contact technical support engineers.
200	OSM.01010026	Get businessType fail.	Failed to obtain the problem type.	Contact technical support engineers.
200	OSM.01010027	The sourceId does not exist.	Source ID does not exist.	Check the source ID, or contact technical support engineers.
200	OSM.01010028	The businessTypeId is not exist.	Problem type ID does not exist.	Query the problem type ID.
200	OSM.01010029	Get caseType fail.	Failed to obtain the service ticket type.	Contact technical support engineers.
200	OSM.01010030	The caseTypeId does not exist.	Service ticket type ID does not exist.	Check the service ticket type ID.
200	OSM.01010031	The type is invalid.	Illegal type.	Check the type, or contact technical support engineers.
200	OSM.01010032	The authorization detail id does not exist.	Authorization item ID does not exist.	Check the authorization item ID, or contact technical support engineers.
200	OSM.01010033	The regionId does not exist.	Region ID does not exist.	Check the region ID, or contact technical support engineers.
200	OSM.01010034	The status is illegal for this operation.	Illegal status.	Check the status, or contact technical support engineers.
200	OSM.01010035	No group operation permission.	You do not have the permission to handle service tickets in the same group.	Add the permission to handle service tickets in the same group, or contact technical support engineers.
200	OSM.01010036	Exceeded the number of times the verification code can be sent.	The number of verification codes sent has reached the upper limit.	Refer to the error description, or contact technical support engineers.
200	OSM.01010037	Exceeded the number of times the case limit was created.	The number of created service tickets has exceeded the upper limit.	Refer to the error message, or contact technical support engineers.
200	OSM.01010038	Exceeded the number of times the case limit was created per day.	The number of created service tickets has exceeded the upper limit on a day.	Refer to the error description, or contact technical support engineers.
200	OSM.01010039	The label id does not exist.	The label ID does not exist.	Check the label ID.
200	OSM.01010040	LabelName already exist.	Label names cannot be repeated.	Change the label name and submit again.
200	OSM.01010041	The same domainId labels should not be over 30.	A single tenant cannot have more than 30 labels.	Refer to the error description, or contact technical support engineers.
200	OSM.01010042	The same caseId labels should not be over 5.	A ticket can associate no more than 5 labels.	Delete the labels number to 5 or fewer.
200	OSM.01010043	The same caseId relations should not be over 3.	A ticket can be associated with only 3 other tickets.	Delete associated tickets so that the total number of associated tickets is equal to or less than 3.
200	OSM.01010044	The case cannot be bound with itself.	A ticket cannot be associated with itself.	Refer to the error message, or contact technical support engineers.
200	OSM.01010045	The accessory is invalid.	Illegal attachment.	Refer to the error message, or contact technical support engineers.
200	OSM.01010046	Re-apply and withdraw and Reject and Agree only if the authorization is pending status.	You can resend, cancel, reject, or agree to authorization only when it is in progress.	Refer to the error message, or contact technical support engineers.
200	OSM.01010047	Target host connection timed out.	Connection to the target host timed out.	Refer to the error message, or contact technical support engineers.