Error Code
Last Updated：2020-07-20
The detailed error information is returned through Response Body in case of a request error, and the following format is followed:
| Parameter name | Type | Description |
|---|---|---|
| code | String | Error code |
| message | String | Err description |
| requestId | String | RequestID of this request |
Example:
{
"requestId" : "ae2225f7-1c2e-427a-a1ad-5413b762957d",
"code" : "NoSuchKey",
"message" : "The resource you requested does not exist"
}BCE Common Error Code
Common error codes of Baidu AI Cloud APIs are listed in the following table.
| Code | Message | HTTP Status Code | Description |
|---|---|---|---|
| AccessDenied | Access denied. | 403 Forbidden | 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 doesn't meet the requirements semantically, such as lack of one necessary item or value type mismatch. For consideration of compatibility, all unrecognizable items should be ignored directly, and this error should not be returned. |
| InternalError | We encountered an internal error. Please try again. | 500 Internal Server Error | All other undefined errors should not be utilized when there are specific corresponding other types of errors (including generic and service customized errors). |
| InvalidAccessKeyId | The Access Key ID you provided does not exist in our records. | 403 Forbidden | Access Key ID does not exist |
| InvalidHTTPAuthHeader | The HTTP authorization header is invalid. Consult the service documentation for details. | 400 Bad Request | Authorization header format is incorrect |
| InvalidHTTPRequest | There was an error in the body of your HTTP request. | 400 Bad Request | The HTTP body format is wrong. E.g. inconformity with the designated Encoding, etc. |
| InvalidURI | Could not parse the specified URI. | 400 Bad Request | The URI format is incorrect, such as mismatch of some service-defined keywords. For ID mismatch and other problems, a more specific error code should be defined, such as NoSuchKey. |
| MalformedJSON | The JSON you provided was not well-formed. | 400 Bad Request | JSON format is invalid |
| InvalidVersion | The API version specified was invalid. | 404 Not Found | URI version No. is invalid |
| OptInRequired | A subscription for the service is required. | 403 Forbidden | Corresponding service is not enabled |
| PreconditionFailed | The specified If-Match header doesn't match the ETag header. | 412 Precondition Failed | For details, please see [Using ETag](# etag) |
| RequestExpired | Request has expired. Timestamp date is XXX. | 400 Bad Request | Request timeout XXX shall be changed to the value of [x-bce-date](#req_header_x-bce-date). If there is only Date in the request, you need to convert Date to [format specified in this specification](#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 non-identical. |
| 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 in the Authorization header is inconsistent with the server authentication. |
Hosteye Service Error Code
| Error code | Err description | HTTP status code | Semantics |
|---|---|---|---|
| ReadBccDenied | No read bcc permission | 403 | No permission to read bcc |
| OperateBccDenied | No operate bcc permission | 403 | No permission to operate bcc |
| ReadHosteyeDenied | No read hosteye permission | 403 | No permission to read hosteye |
| OperateHosteyeDenied | No operate hosteye permission | 403 | No permission to operate hosteye |
| AdminHosteyeDenied | No admin hosteye permission | 403 | No permission to administrate hosteye |