Common error codes for image analysis and processing
If an API request fails, the server returns an error message. This topic describes the error codes for the image analysis and processing API.
If you have questions about API access, usage, or other issues related to the Alibaba Cloud Visual Intelligence API, join the Alibaba Cloud Visual Intelligence API consultation DingTalk group (ID: 23109592).
Troubleshooting center
Use the Troubleshooting Center to efficiently diagnose problems with API calls.
Image analysis and processing error codes
Status code | Error code | Description |
403 | AuthFailed | Authorization failed. Check your RAM permission configuration. |
400 | ClientError.IllegalArgument | Check the parameters. For example, check if the database represented by the parameter value exists. |
400 | EntityNotExist.Role | You do not have RAM permissions. Contact the root account to grant you the AliyunVIAPIFullAccess permission. For more information, see Control access using RAM policies. |
400 | IllegalUrlParameter | The URL is invalid. Check if the URL can be opened. For image URLs that are not for OSS in the China (Shanghai) region, see Handle file URLs. |
500 | InternalError | An internal server error occurred. If this affects your business, contact us through the DingTalk group (ID: 23109592). |
500 | InternalError.Algo | An internal algorithm processing error occurred. If this affects your business, contact us through the DingTalk group (ID: 23109592). |
500 | InternalError.Timeout | The algorithm service timed out during internal processing. Retry later. If this affects your business, contact us through the 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 | InvalidAccessKeyId.NotFound | The AccessKey ID was not found. Check if the AccessKey ID and AccessKey secret are correct. |
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 was not found. Check if the category and capability match, and if the endpoint and capability match. For more information, see Endpoints. Select a programming language and modify the sample code to integrate the API. For more information, see SDK overview. |
400 | InvalidApi.ForbiddenInvoke | The call is restricted. Check if the capability you are calling is restricted. For restricted capabilities, you must find the capability in the console and submit a request. You can call the capability only after it is approved or manually activated. If this is not the case, check if 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 | Check the file content against the algorithm documentation. Replace the file with one that meets the algorithm's 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 URLs 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 URLs 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 | The file type is incorrect. Check the file type and use a type supported by the algorithm, as described in the API documentation. Alibaba Cloud Visual Intelligence API reads the file to get its true type, rather than relying on the file extension. Checking only the file extension is not effective. 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 URLs that are not for OSS in the China (Shanghai) region, see Handle file URLs. |
400 | InvalidImage.Content | Check the image content against the algorithm documentation. Replace the image with one that meets the algorithm's requirements. |
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 URLs that are not for OSS in the China (Shanghai) region, see Handle file URLs. URLs do not support spaces or Chinese characters. If a URL contains these characters, encode it using URLEncode before passing it. |
404 | InvalidImage.NotFoundFace | No face was found in the image. Check if your image contains a face or if the face is too small. |
400 | InvalidImage.REGION | The region of the image link is incorrect. For image URLs that are not for OSS in the China (Shanghai) region, see Handle file URLs. |
400 | InvalidImage.Resolution | The file resolution exceeds the limit. Check the file resolution and content. Modify the file resolution and retry. |
400 | InvalidImage.Timeout | The image download timed out. Check your on-premises network, if the link is accessible, and if the OSS link has expired. For image URLs that are not for OSS in the China (Shanghai) region, see Handle file URLs. |
400 | InvalidImage.Type | The image type is incorrect. Check the image type and use a type supported by the algorithm, as described in the API documentation. |
400 | InvalidImage.URL | The image link is invalid. Check if the image link is accessible. For image URLs 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 currently supported. |
426 | InvalidParameter | Fewer than 10 images were provided. The images cannot be analyzed. |
425 | InvalidParameter | The data contains non-axial data and cannot be analyzed. |
424 | InvalidParameter | The data contains multiple sequences and cannot be analyzed. |
423 | InvalidParameter | Non-DICOM data was passed. |
422 | InvalidParameter | The DICOM data is empty. |
421 | InvalidParameter | The data contains subdirectories and cannot be processed. |
400 | InvalidParameter.BadRequest | A parameter is incorrect. Check the parameter value against the API documentation and the error message. Check for extra spaces or other special characters before or after the parameter value. |
400 | InvalidParameter.NotFound | A parameter is incorrect. Check the parameter value against the API documentation and the error message. Check for extra spaces or other special characters before or after the parameter value. |
400 | InvalidParameter.TooLarge | A parameter is incorrect. The file size exceeds the limit. Adjust the file size as described in the API documentation. |
400 | InvalidRamRole | You do not have RAM permissions. Contact the root account to grant you the AliyunVIAPIFullAccess permission. For more information, see Control access using RAM policies. |
400 | InvalidResult | A parameter is incorrect. Check the parameter value and file content against the documentation. For example, check if the image content is incomplete or too blurry. |
400 | InvalidSide | The specified parameter `Side` is not valid. Enter a valid value for the `Side` parameter as described in the documentation. |
400 | InvalidTimeStamp.Expired | The timestamp has expired. Update the timestamp. |
400 | MissingAccessKeyId | The AccessKey ID is missing. Check if the AccessKey ID and AccessKey secret are correct. |
400 | MissingParameter | A parameter is missing. Check the parameter values against the documentation. |
400 | ParameterError | A parameter is incorrect. Check the parameter value. |
503 | ServiceUnavailable | The service is unavailable. If the server has returned a RequestId, contact us through the DingTalk group (ID: 23109592). |
400 | SignatureDoesNotMatch | The signature is incorrect. Recalculate the signature. For more information, see Request signing. |
400 | SignatureNonceUsed | The signature nonce has already been used. Recalculate the signature. For more information, see Request signing. |
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 (ID: 23109592). Note When throttling is triggered, both `Throttling` and `Throttling.User` may occur. Consider both when handling the error. |
408 | Timeout | The request timed out. |
403 | Unauthorized | You do not have RAM permissions. Contact the root account to grant you the AliyunVIAPIFullAccess permission. For more information, see Control access using RAM policies. |
400 | Throttling | Throttling was triggered. For paid APIs, purchase a higher QPS. For free APIs with special requirements, contact us through the DingTalk group (ID: 23109592). Note When throttling is triggered, both `Throttling` and `Throttling.User` may occur. Consider both when handling the error. |
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 description of the error code to identify the cause and find a solution. The following suggestions can help you troubleshoot common error types.
URL-related error codes
These error codes 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 are also related to URLs and can be caused by issues such as image download failures or region mismatches. We recommend that you use the China (Shanghai) region. If you generate a URL using Object Storage Service (OSS), the OSS bucket must also be in the China (Shanghai) region. For more information, see Handle file URLs.
Parameter-related error codes
These error codes usually indicate that the input parameters do not meet the requirements, such as missing parameters or incorrect parameter types. Verify that your input parameters comply with the requirements in the request parameters table of the corresponding API document.
System service error codes
If this type of error occurs, retry the service request. If the error persists, report the issue in the DingTalk group (ID: 23109592).