Common error codes for object detection
When an API request fails, the server returns an error message. This topic describes the error codes returned by the Object Detection API.
If you have questions about API access, interface usage, or other issues related to the Alibaba Cloud Visual Intelligence API, join the Alibaba Cloud Visual Intelligence API consultation DingTalk group (23109592) to contact us.
Troubleshooting center
You can use the Troubleshooting Center to efficiently diagnose problems with API calls.
Object detection error codes
Status code | Error code | Description |
403 | AuthFailed | Authorization failed. Check your RAM permission configuration. |
400 | ClientError.IllegalArgument | Invalid request parameter. For more information, see the error message. |
409 | Data.Exist | The data already exists. |
400 | EntityNotExist.Role | You do not have RAM permissions. Contact your Alibaba Cloud account to grant you the AliyunVIAPIFullAccess permission. For more information, see Control access using RAM policies. |
400 | IllegalUrlParameter | The URL is invalid. Check whether the URL can be opened. For image URLs that are not for OSS in the China (Shanghai) region, see Process file URLs. |
500 | InternalError | An internal server error occurred. If this affects your business, contact us through the DingTalk group (23109592). |
500 | InternalError.Algo | An internal algorithm processing error occurred. If this affects your business, contact us through the DingTalk group (23109592). |
500 | InternalError.Convert | Failed to transform the input parameter. If this affects your business, contact us through the DingTalk group (23109592). |
500 | InternalError.Decode | Image decoding failed. If this affects your business, contact us through the DingTalk group (23109592). |
500 | InternalError.Env | Failed to initialize the environment. If this affects your business, contact us through the DingTalk group (23109592). |
500 | InternalError.Mapping | An internal algorithm processing error occurred. If this affects your business, contact us through the DingTalk group (23109592). |
500 | InternalError.Model | Model loading error. If this affects your business, contact us through the DingTalk group (23109592). |
500 | InternalError.Process | An abnormal inference procedure occurred. If this affects your business, contact us through the DingTalk group (23109592). |
500 | InternalError.Timeout | The algorithm service timed out during internal processing. Try again later. If this affects your business, contact us through the DingTalk group (23109592). |
500 | InternalError.Transfer | Failed to download or upload data. Try again later. If this affects your business, contact us through the DingTalk group (23109592). |
400 | InvalidAccessKeyId.Inactive | The AccessKey ID is invalid. Check whether the AccessKey ID is disabled, or whether the AccessKey ID and AccessKey secret are correct. |
400 | InvalidAccessKeyId.NotFound | The AccessKey ID was not found. Check whether the AccessKey ID and AccessKey secret are correct. |
400 | InvalidAccessKeySecret | The AccessKey ID or AccessKey secret is incorrect. Check whether the AccessKey ID and AccessKey secret are correct. |
400 | InvalidAction.NotFound | The capability was not found. Check whether the category and capability match, and whether the endpoint and capability match. For more information, see Endpoints. Select a programming language and modify the sample code to make the API call. For more information, see SDK overview. |
400 | InvalidApi.ForbiddenInvoke | The call is restricted. Check whether the capability you are calling is restricted. For restricted capabilities, you must find the capability in the console and request access. You can call the capability only after the request is approved or you manually activate it. If this is not the case, check whether your account has an overdue payment. |
400 | InvalidApi.NotPurchase | The service is not activated. Activate the service first. |
400 | InvalidApi.OutOfService | The product is not activated. Activate the product. |
400 | InvalidFile.Content | The content format of the image or video file is incorrect. |
400 | InvalidFile.Decode | File decoding failed. |
400 | InvalidFile.Download | The file cannot be downloaded. Check your on-premises network and whether the URL is accessible. For file URLs that are not for OSS in the China (Shanghai) region, see Process file URLs. |
400 | InvalidFile.Region | The file URL format is incorrect. It must be an OSS file address in the same region as your Alibaba Cloud service. |
400 | InvalidFile.Resolution | The resolution of the image or video is incorrect. |
400 | InvalidFile.Type | Incorrect file type. Check the file type and use a type supported by the algorithm. For more information, see the API documentation for the algorithm. Alibaba Cloud Visual Intelligence API reads the file to get the actual file type instead of judging by the file extension. Checking only the file extension is not effective. For more information about file type detection and processing, see Detect and process file types. |
400 | InvalidFile.URL | The file URL format is incorrect. It must be an OSS file address in the same region as your Alibaba Cloud service. |
400 | InvalidImage.Content | Check the image content by referring to the algorithm documentation. Replace the image with one that meets the algorithm's requirements. |
400 | InvalidImage.Decode | The content format of the image or video file is incorrect. |
400 | InvalidImage.Download | The image cannot be downloaded. Check your on-premises network, whether the URL is accessible, and whether the OSS URL has expired. For image URLs that are not for OSS in the China (Shanghai) region, see Process file URLs. URLs do not support spaces or Chinese characters. If a URL contains them, encode the URL before passing it. |
404 | InvalidImage.NotFound | The image file specified in the parameter does not exist. |
404 | InvalidImage.NotFoundFace | No face was detected in the input image. |
400 | InvalidImage.Region | The file URL format is incorrect. It must be an OSS file address in the same region as your Alibaba Cloud service. |
400 | InvalidImage.Resolution | The resolution of the image or video is incorrect. |
400 | InvalidImage.Timeout | File download timed out. |
400 | InvalidImage.Type | Incorrect image type. Check the image type and use a type supported by the algorithm. For more information, see the API documentation for the algorithm. |
400 | InvalidImage.URL | The image URL is invalid. Check whether the image URL is accessible. For image URLs that are not for OSS in the China (Shanghai) region, see Process file URLs. For OSS URLs in the China (Shanghai) region, use standard OSS domain names. Accelerated domain names and custom domain names are not supported. |
400 | InvalidParameter | Invalid request parameter. |
400 | InvalidParameter.BadRequest | The request parameter or data is incorrect. |
400 | InvalidParameter.NotFound | The requested data does not exist. |
400 | InvalidParameter.TooLarge | The file size exceeds the limit. |
400 | InvalidParameter.Type | The data format of the request parameter is incorrect. |
400 | InvalidParameter.Unsuitable | The data is empty or cannot be processed. |
400 | InvalidParamter.Type | The data format of the request parameter is incorrect. |
400 | InvalidRamRole | You do not have RAM permissions. Contact your Alibaba Cloud account to grant you the AliyunVIAPIFullAccess permission. For more information, see Control access using RAM policies. |
400 | InvalidResult | Invalid parameter. Check the parameter value and file content by referring to the documentation. Check whether the image content is incomplete or too blurry. |
400 | InvalidSide | Specified parameter Side is not valid. Enter a correct value for the Side parameter by referring to the documentation. |
400 | InvalidTimeStamp.Expired | The timestamp has expired. Update the timestamp. |
400 | MissingAccessKeyId | The AccessKey ID is not specified. Check whether the AccessKey ID and AccessKey secret are correct. |
400 | MissingParameter | A request parameter is missing. |
400 | ParameterError | Invalid parameter. Check the parameter value. |
400 | QuotaExceeded.DbCount | The number of databases exceeds the limit. |
400 | QuotaExceeded.FaceGroupCount | The number of databases exceeds the limit. |
400 | QuotaExceeded.FaceImageCount | The number of faces or traces exceeds the limit. |
400 | QuotaExceeded.ImageCount | The number of faces or traces exceeds the limit. |
449 | Retry | The request failed due to an occasional issue, such as network jitter. You need to retry the request. |
400 | SDK.ServerUnreachable | An SDK-side error occurred. |
503 | ServiceUnavailable | The service is unavailable. If the server has returned a RequestId, contact us through the DingTalk group (23109592). |
500 | ServiceUnavailable | A network request error occurred. First, check for faults in your on-premises network, such as the local area network. If the server has returned a RequestId, contact us through the DingTalk group (23109592). |
400 | SignatureDoesNotMatch | The signature is incorrect. Recalculate the signature. For more information, see Request signature. |
400 | SignatureNonceUsed | The signature has already been used. Recalculate the signature. For more information, see Request signature. |
400 | Throttling | Throttling was triggered. For paid APIs, purchase a higher QPS. For free APIs with special requirements, contact us through the DingTalk group (23109592). Note When throttling is triggered, both `Throttling` and `Throttling.User` may occur. Consider both when handling the error. |
400 | Throttling.User | The traffic for this period has exceeded the limit. For paid APIs, purchase a higher QPS. For free APIs with special requirements, contact us through the DingTalk group (23109592). Note When throttling is triggered, both `Throttling` and `Throttling.User` may occur. Consider both when handling the error. |
408 | Timeout | The request or processing timed out. |
403 | Unauthorized | RAM permission verification failed. For more information, see Control access using RAM policies. |
Common error codes
For common API error codes, see API Error Center.
Suggestions
If a service request returns an error code, refer to the error code description to identify the cause and resolve the error. The following suggestions are provided for common error types.
URL-related error codes
These errors usually indicate that the file URL does not meet the requirements. For example, the URL may be insecure or invalid. For more information, see Process file URLs.
Image loading error codes
These errors are often caused by issues with the image URL, such as image download failures or incorrect region settings. We recommend that you use the China (Shanghai) region. If you generate a URL using OSS, the bucket that you create in OSS must also be in the China (Shanghai) region. For more information, see Process file URLs.
Parameter-related error codes
These errors usually indicate that the input parameters do not meet the requirements, such as missing parameters or incorrect parameter types. Check that your input parameters meet the requirements by referring to the request parameters table in the corresponding API documentation.
System service error codes
If this type of error occurs, try sending the service request again. If the problem persists, provide feedback in the DingTalk group (23109592).