Error code
Updated at：2025-11-11
Error code format
When an error is encountered during API access, the corresponding error code and information will be returned to identify and address the issue. If a request error occurs, detailed error information is provided within the Response Body, formatted as follows:
| Parameter name | Types | Description |
|---|---|---|
| code | String | Specify the exact error type. |
| message | String | Provide a detailed description of the error. |
| requestId | String | The requestId that caused the error. |
For example:
Plain Text
1{
2 "code":"IllegalRequestUrl",
3 "message":"The requested url belongs to domain which is not under acceleration",
4 "requestId":" 81d0b05f-5ad4-1f22-8068-d5c9de60a1d7"
5}Global error codes
| Error code | Error message | HTTP status code | Description |
|---|---|---|---|
| AccessDenied | Access denied. | 403 Forbidden | You do not have permission to access this resource. |
| 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 syntactically correct but semantically invalid. For example, a required item might be missing, or the value type might be mismatched. For compatibility, all unrecognized items should be ignored, and this error should not be returned. |
| InternalError | We encountered an internal error. Please try again. | 500Internal Server Error | All other undefined errors. This should not be used if there are clearly corresponding errors of other types, including both general and service-specific errors. |
| 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 format is invalid. |
| InvalidHTTPRequest | There was an error in the body of your HTTP request. | 400 Bad Request | The HTTP body format is invalid, for example, it could be due to incompatible Encoding. |
| InvalidURI | Could not parse the specified URI. | 400 Bad Request | The URI format is invalid. For instance, predefined service-specific keywords may not be correct. For issues like ID mismatching, more specific error codes like NoSuchKey should be applied. |
| MalformedJSON | The JSON you provided was not well-formed. | 400 Bad Request | The JSON format is invalid. |
| InvalidVersion | The API version specified was invalid. | 404 Not Found | The URI version number is invalid. |
| OptInRequired | A subscription for the service is required. | 403 Forbidden | The corresponding service has not been activated. |
| PreconditionFailed | The specified If-Match header doesn't match the ETag header. | 412 Precondition Failed | Refer to the ETag header. |
| RequestExpired | Request has expired. Timestamp date is XXX. | 400 Bad Request | Request timeout. Replace XXX with the value of x-bce-date. If only the Date is used in the request, it must be converted to datetime. |
| IdempotentParameterMismatch | The request uses the same client token as a previous, but non-identical request. | 403 Forbidden | The API parameters do not match for the same clientToken. |
| 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 in the Authorization header does not match the server's verification. |