Error Code
Last Updated：2021-11-23
Error Code Format
If an error occurs when you access API, it returns the corresponding error code and error information, to facilitate you to locate the problem and take appropriate measures. When an error occurs in the request, the detailed error message is returned via the Response Body in the format below:
| Parameter Name | Type | Description | | --------- | ------ | ----------------------- | | code | String | It indicates the specific error type. | | message | String | Detailed description of this error. | | requestId | String | Means the requestId causing the error. | For example:
{
"code":"IllegalRequestUrl",
"message":"The requested url belongs to domain which is not under acceleration",
"requestId":" 81d0b05f-5ad4-1f22-8068-d5c9de60a1d7"
}Common Error Code
| Error code | Error Message | HTTP states code | Description |
|---|---|---|---|
| AccessDenied | Access denied. | 403 Forbidden | You’ve no permission to access corresponding resources. |
| InappropriateJSON | The JSON you provided was well-formed and valid, but not appropriate for this operation. | 400 Bad Request | The JSON format in the request is correct, but its semantics does not meet the requirements. For example, a required item is missing, or the value type does not match. Considering compatibility, all unrecognized items shall be directly ignored and this error shall not be returned. |
| InternalError | We encountered an internal error Please try again. | 500Internal Server Error | Means all other undefined errors. When other types of corresponding errors (including common and service-customized errors) are available, this type of error needs to be avoided. |
| InvalidAccessKeyId | The Access Key ID you provided does not exist in our records. | 403 Forbidden | The Access Key ID does not exist. |
| InvalidHTTPAuthHeader | The HTTP authorization header is invalid. Consult the service documentation for details. | 400 Bad Request | The Authorization header field format is error. |
| InvalidHTTPRequest | There was an error in the body of your HTTP request. | 400 Bad Request | The format of the HTTP body is incorrect. For example, it does not conform to the specified Encoding etc. |
| InvalidURI | Could not parse the specified URI. | 400 Bad Request | URI form is incorrect. For example, the keywords defined by some services are not matched. For problems such as ID mismatch, more specific error codes should be defined, such as NoSuchKey. |
| MalformedJSON | The JSON you provided was not well-formed. | 400 Bad Request | The JSON format is illegal. |
| InvalidVersion | The API version specified was invalid. | 404 Not Found | URI version number is illegal. |
| OptInRequired | A subscription for the service is required. | 403 Forbidden | No corresponding service has been opened. |
| PreconditionFailed | The specified If-Match header doesn’t match the ETag header. | 412 Precondition Failed | See ETag. |
| RequestExpired | Request has expired. Timestamp date is XXX. | 400 Bad Request | The request timeout. XXX is changed to an xbcedate value. If there is only Date in the request, you need to change Date to datetime. |
| IdempotentParameterMismatch | The request uses the same client token as a previous, but non-identical request. | 403 Forbidden | The API parameters corresponding to clientToken are different. |
| SignatureDoesNotMatch | The request signature we calculated does not match the signature you provided. Check your Secret Access Key and signing method. Consult the service documentation for details. | 400 Bad Request | The signature attached to the Authorization header field is inconsistent with the server verification. |