This topic describes the error codes that the server returns when a Face and Body API request fails.
If you have questions about API integration, usage, or other issues related to the Alibaba Cloud Visual Intelligence API, contact us by joining our DingTalk group (ID: 23109592).
Troubleshooting center
Use the Troubleshooting Center to efficiently diagnose API issues.
Face and body error codes
Status code | Error code | Description |
403 | AuthFailed | Authorization failed. Check your RAM permission configuration. |
400 | ParameterError | Invalid parameter. Check the parameter value. |
400 | ClientError.IllegalArgument | Check the parameters. For example, confirm that the database specified by the parameter value exists. |
400 | EntityNotExist.Role | RAM permission is missing. Contact the root account to grant you the AliyunVIAPIFullAccess permission. For more information, see Control access permissions using RAM policies. |
400 | IllegalUrlParameter | The URL is invalid. Check if the URL can be opened. For image links that are not for OSS in the China (Shanghai) region, see Handle file URLs. |
500 | InternalError | Internal server error. If your business is affected, contact us through our DingTalk group (ID: 23109592). |
500 | InternalError.Algo | Internal algorithm processing error. If your business is affected, contact us through our DingTalk group (ID: 23109592). |
500 | InternalError.Timeout | Internal processing timeout error. If your business is affected, contact us through our DingTalk group (ID: 23109592). |
400 | InvalidAccessKeyId.Inactive | The AccessKey ID is invalid. Check if the AccessKey ID is disabled, or if the AccessKey ID and AccessKey secret are correct. |
400 | InvalidDB.Status | The database status is invalid. The database is frozen. To restore it, contact us through our DingTalk group (ID: 23109592). |
404 | InvalidAccessKeyId.NotFound | The AccessKey ID does not exist. Check if you used the correct AccessKey in the call. For more information, see Create an AccessKey. |
400 | InvalidAccessKeySecret | The AccessKey ID or AccessKey secret is incorrect. Check if the AccessKey ID and AccessKey secret are correct. |
400 | InvalidAction.NotFound | The capability is not found. Check if the category and capability match. Also, check if the endpoint and capability match. For more information, see Endpoints. To integrate, select a programming language and modify the sample code. For more information, see SDK overview. |
400 | InvalidApi.ForbiddenInvoke | The call is restricted. Check if the capability you are calling is restricted. Restricted capabilities must be requested in the console. You can call them only after approval or manual activation. If this is not the case, check for overdue payments in your account. |
403 | InvalidApi.NotPurchase | The product is not activated. Activate the product. |
400 | InvalidApi.OutOfService | The product is not activated. Activate the product. |
400 | InvalidFile.Content | Check the file content against the algorithm documentation. Replace the file with one that meets the algorithm requirements. |
400 | InvalidFile.Decode | Check if the file can be opened. |
400 | InvalidFile.Download | The file cannot be downloaded. Check your on-premises network and if the link is accessible. For file links that are not for OSS in the China (Shanghai) region, see Handle file URLs. |
400 | InvalidFile.REGION | The region of the file link is incorrect. For file links that are not for OSS in the China (Shanghai) region, see Handle file URLs. |
400 | InvalidFile.Resolution | The file resolution exceeds the limit. Check the file resolution and content. Modify the file resolution and retry. |
400 | InvalidFile.Type | Invalid file type. Check the file type. Use a file type supported by the algorithm as described in the API documentation. The Alibaba Cloud Visual Intelligence API reads the file to get its true type, instead of judging by the file extension. Checking only the file extension is not valid. For more information about how to check and handle file types, see Check and handle file types. |
400 | InvalidFile.URL | The file cannot be downloaded. Check your on-premises network and if the link is accessible. For file links that are not for OSS in the China (Shanghai) region, see Handle file URLs. |
400 | InvalidImage.Category | The input image does not match the current service. For example, the input image for the vehicle license service is not a vehicle license. |
400 | InvalidImage.Content | The input image content is invalid. Examples: The image is an invalid Base64-encoded image. The input image is an empty string. The image content is invalid. The image failed to be decoded. The input image is not a valid Base64 string. Remove the extra header from the Base64 string, such as `data:image/jpg:base64`. The length of Base64-encoded data must be a multiple of 4. If not, pad the end with |
400 | InvalidImage.Decode | Check if the image can be opened. |
400 | InvalidImage.Download | The image cannot be downloaded. Check your on-premises network, if the link is accessible, and if the OSS link has expired. For image links that are not for OSS in the China (Shanghai) region, see Handle file URLs. URLs do not support spaces or Chinese characters. If they are included, URLEncode them before passing them in. |
400 | InvalidImage.Gif | Failed to open, read, or decode the GIF image. Or, an error occurred when getting the color mapping table, or the image is empty. |
404 | InvalidImage.NotFoundFace | No face was found in the image. Check if your image contains a face or if the face is too small. If a face is present, contact us through our DingTalk group (ID: 23109592). |
400 | InvalidImage.Region | The image is in the wrong region. |
400 | InvalidImage.Resolution | The file resolution exceeds the limit. Check the file resolution and content. Modify the file resolution and retry. |
400 | InvalidImage.Timeout | Image download timed out. Check your on-premises network, if the link is accessible, and if the OSS link has expired. For file links that are not for OSS in the China (Shanghai) region, see Handle file URLs. |
400 | InvalidImage.Type | Invalid image type. Check the image type. Use an image type supported by the algorithm as described in the API documentation. |
400 | InvalidImage.Unsafe | The URL is not secure. |
415 | InvalidImage.UnsupportedMediaType | The input image failed to be decoded. |
400 | InvalidImage.URL | The image link is invalid. Check if the image link is accessible. For image links that are not for OSS in the China (Shanghai) region, see Handle file URLs. For OSS links in the China (Shanghai) region, use standard OSS domain names. Accelerated domain names and custom domain names are not supported. |
400 | InvalidImageType | Invalid image type. |
400 | InvalidOutputFormat | Invalid output format. |
400 | InvalidParameter | The parameter value failed verification. Use the request parameters to construct a standardized query string in the request. For more information, see Request signing. |
400 | InvalidParameter.BadRequest | Invalid parameter. Check the parameter value against the API documentation and the error message. For example, check for extra spaces or other special characters before or after the parameter value. |
400 | InvalidParameter.NotFound | Invalid parameter. Check the parameter value against the API documentation and the error message. For example, check for extra spaces or other special characters before or after the parameter value. |
400 | InvalidParameter.TooLarge | The content to be detected is too large. Make sure the content is within the API limits. |
400 | InvalidRamRole | RAM permission is missing. Contact the root account to grant you the AliyunVIAPIFullAccess permission. For the procedure, see Control access permissions using RAM policies. |
400 | InvalidResult | OCR detection failed or was abnormal. |
400 | InvalidSide | The Side parameter is invalid. |
400 | InvalidTimeStamp.Expired | The difference between the user time and the server time is more than 15 minutes. Check your timestamp settings to make sure the difference is within 15 minutes. |
400 | MissingAccessKeyId | The AccessKey ID is missing. For more information, see Create an AccessKey. |
400 | MissingAssureDirection | The AssureDirection parameter is missing. |
400 | MissingImageURL | The image URL parameter is missing. |
400 | MissingMinHeight | The MinHeight parameter is missing. |
400 | MissingOutputFormat | The output format is missing. |
400 | MissingParameter | A parameter is missing. Check the parameter values against the documentation. |
400 | QuotaExceeded.ImageCount | The number of faces or traces exceeds the limit. Check the limits in the documentation. To adjust the limits, contact us through our DingTalk group (ID: 23109592). |
400 | QuotaExceeded.FaceImageCount | The number of faces or traces exceeds the limit. Check the limits in the documentation. To adjust the limits, contact us through our DingTalk group (ID: 23109592). |
400 | QuotaExceeded.FaceGroupCount | The number of databases exceeds the limit. Check the limits in the documentation. To adjust the limits, contact us through our DingTalk group (ID: 23109592). |
400 | QuotaExceeded.DbCount | The number of databases exceeds the limit. Check the limits in the documentation. To adjust the limits, contact us through our DingTalk group (ID: 23109592). |
449 | Retry | The request failed due to an occasional issue, such as network jitter. Retry the request. |
400 | SDK.ServerUnreachable | SDK-side error. |
503 | ServiceUnavailable | The service is unavailable. If the server returned a RequestId, contact us through our DingTalk group (ID: 23109592). |
500 | ServiceUnavailable | Network request error. First, check for faults in your on-premises network, such as the local area network. If the server returned a RequestId, contact us through our DingTalk group (ID: 23109592). |
500 | InternalError.Mapping | Internal algorithm processing error. If your business is affected, contact us through our DingTalk group (ID: 23109592). |
400 | SignatureDoesNotMatch | The signature is incorrect. Recalculate the signature. For more information, see Request signing. |
400 | SignatureNonceUsed | The signature has already been used. Recalculate the signature. For more information, see Request signing. |
400 | Throttling | Throttling was triggered. For paid APIs, purchase a higher QPS. For free APIs with special requirements, contact us through our DingTalk group (ID: 23109592). Note When throttling is triggered, both Throttling and Throttling.User errors can 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 our DingTalk group (ID: 23109592). Note When throttling is triggered, both Throttling and Throttling.User errors can 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 permissions using RAM policies. |
403 | UnsupportedHTTPMethod | The HTTP request method is not supported. Review the API call method documentation for each product. |
Common error codes
For common API error codes, see the API Error Center.
Troubleshooting 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 can help you resolve common errors.
URL-related error codes
These errors usually indicate that the file URL does not meet the specified requirements. For example, the URL may be insecure or invalid. For more information, see Handle file URLs.
Image loading error codes
These errors, such as image download errors or region errors, are often related to image URLs. 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 Handle 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. To resolve these errors, check whether your input parameters meet the requirements that are described in the request parameters table of the relevant API reference.
System service error codes
If this type of error occurs, retry the service request. If the problem persists, contact us in our DingTalk group (ID: 23109592).