Error code
Updated at：2025-10-16
When a request error occurs, detailed error information is returned through the response body in the format below:
| Parameter name | Types | Description |
| code | String | Error code |
| message | String | Error description |
| requestId | String | Request ID of this request |
| Parameter name | Types | Description |
|---|---|---|
| code | String | Error code |
| message | String | Error description |
| requestId | String | Request ID of this request |
Example:
Plain Text
1 {
2 "requestId" : "ae2225f7-1c2e-427a-a1ad-5413b762957d",
3 "code" : "NoSuchKey",
4 "message" : "The resource you requested does not exist"
5 }BCE global error codes
| Error return codes | Error message | 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 correct but semantically invalid Requirements. For example, any required item is missing or the value type does not match, etc. etc. For compatibility, all unrecognized items should be directly ignored without returning this error. |
| InternalError | We encountered an internal error. Please try again. |
500 Internal Server Error |
All other undefined errors. Where there is a clear corresponding error of other types (including generic and self-defined services) , it should not be used. |
| InvalidAccessKeyId | The Access Key ID you provided does not exist in our records. | 403 Forbidden | The Access Key ID does not exist. |
| InvalidHTTPAuthHeader | The Access Key ID you provided does not exist in our records. | 400 Bad Request | The authorization header format is invalid. |
| InvalidHTTPRequest | There was an error in the body of your HTTP request. |
400 Bad Request |
Invalid HTTP body format. e.g., non-compliant encoding, etc. |
| InvalidURI | Could not parse the specified URI. | 400 Bad Request |
Invalid URI format For example, non-matching with service-defined key words, etc. For problems such as ID mismatches, more specific error codes should be defined, such as NoSuchKey More specific Error Code, such as NoSuchKey. |
| 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 | Please refer to the Etag for more information. |
| RequestExpired | Request has expired. Timestamp date is <Data> . | 400 Bad Request | Request timeout. Replace with x-bce-date. If the request contains only Date, convert the Date 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 |
Signature in the Authorization header doesn’t match server verification Verification inconsistency. |
EIP service error code
| Error code | Error description | HTTP status code | Semantics |
|---|---|---|---|
| InstanceNotFound | The specified instance does not exist. | 404 | The specified instance does not exist |
| EipNotFound | The specified eip does not exist. | 404 | The specified EIP does not exist |
| InstanceAlreadyBind | The specified instance is already binded. | 400 | The specified instance has already been bound |
| UnsupportedEipOperation | The status of specified eip does not support this operation. | 400 | The specified EIP status does not support this type of operation |
| RealNameQualify | The login user is not pass real name qualify | 403 | The current user has not passed certification |
| ExceedLimit | The amount of eip exceed limit | 413 | EIP count exceeds user quota limit |
| PrepayEip | The specified eip is prepay | 400 | Prepaid EIPs cannot be released via API |
| PayFailed | Pay failed when create EIP | 400 | Payment failed when creating EIP |
EIPGROUP service error code
| Error code | Error description | HTTP status code | Semantics |
|---|---|---|---|
| InstanceNotFound | The specified instance does not exist. | 404 | The specified instance does not exist |
| UnsupportedInstanceOperation | The status of specified instance does not support this operation. | 400 | The specified instance status does not support this type of operation |
| RealNameQualify | The login user is not pass real name qualify. | 403 | The current user has not passed certification |
| ExceedEIPGroupLimit | The amount of eip group exceed limit. | 413 | The count of EIPGROUPs exceeds the quota limit of the user |
| EIPGroupPayFailed | Pay failed when create eip group. | 400 | Payment failed when creating EIPGROUP |
| ExceedEIPLimitInGroup | The amount of eip exceed the group bandwidth limit | 400 | The count of EIPs in EIPGROUP exceeds the quota limit of the user |
Bandwidth package service error code
| Error return codes | Error message | HTTP status code | Description |
|---|---|---|---|
| TypeNotMatchError | The bandwidth-packet's binding type is not match the instance type. | 400 | The resource type bound to the bandwidth package does not match the actual resource type. |
| BandwidthOverrun | The sum of bandwidth-packet and bandwidth of the bound bandwidth exceed the limit. | 400 | The total bandwidth of the bandwidth package and its bound bandwidth exceeds the allowable limit. |
| InstanceProductPayTypeError | Bandwidth-packet bound resource payment method only supports prepaid. | 400 | Only the prepay billing type is supported for resources bound to the bandwidth package. |
| ResourceNotExit | The resource or instance of the bandwidth-packet is not exist or has been deleted. | 400 | The bandwidth package either does not exist or has been deleted. |
| RepeatBindingError | The bandwidth-packet is being repeated bound. | 400 | The resource you are trying to bind is already bound to a bandwidth package. |
| TimeFormatIllegal | Time format is illegal. | 400 | Invalid time format. |
| TimeUnreasonableError | Time is not allowed. | 400 | The specified time is outside the allowable range. |