Common error codes for image segmentation
If an API request fails, the server-side returns an error message. This topic describes the error codes for the image segmentation API.
If you have questions about API integration, usage, or other issues related to the visual AI capabilities of the Alibaba Cloud Visual Intelligence API, you can contact us by joining our DingTalk group (23109592).
Troubleshooting center
You can use the Troubleshooting Center to diagnose problems with API calls more efficiently.
Image segmentation 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 whether 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 with 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 Handle 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.Env | Failed to initialize the environment. If this affects your business, contact us through the DingTalk group (23109592). |
500 | InternalError.Model | A model loading error occurred. If this affects your business, contact us through the DingTalk group (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 (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. |
404 | InvalidAccessKeyId.NotFound | The AccessKey ID does not exist. Check whether you used the correct AccessKey for the call. For more information, see Create an AccessKey. |
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 connect. 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. |
403 | 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 requirements. |
400 | InvalidFile.Decode | Check whether the file can be opened. |
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 Handle file URLs. |
400 | InvalidFile.REGION | The region of the file URL 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 | Invalid file type. Check the file type and refer to the algorithm API reference to use a file type that the algorithm supports. The Alibaba Cloud Visual Intelligence API determines the actual file type by reading the file, not by its file extension. Relying only on the file extension is invalid. For more information about file type determination and handling, see File type determination and handling. |
400 | InvalidFile.URL | 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 Handle file URLs. |
400 | InvalidImage.Content | The image content is incorrect. |
400 | InvalidImage.Content | The input image content is invalid. For example: The input image is an empty string, an invalid Base64-encoded image, or has invalid image content. |
400 | InvalidImage.Decode | Check whether the image can be opened. |
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 Handle file URLs. URLs do not support spaces or Chinese characters. If a URL contains these characters, URL-encode it before passing it. |
400 | InvalidImage.Region | The region of the image is incorrect. |
400 | InvalidImage.Resolution | The image resolution does not meet the requirements. You can view the image resolution limits in the documentation for the corresponding API. |
400 | InvalidImage.Timeout | The image download timed out. Check your on-premises network, whether the URL is accessible, and whether the OSS URL has expired. For file 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 an image type supported by the algorithm as described in the API documentation. |
400 | InvalidImage.Unsafe | The URL is not secure. |
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 Handle 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 input parameter. |
400 | InvalidParameter.BadRequest | Invalid parameter. 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.Convert | Failed to transform the input parameter. |
400 | InvalidParameter.NotFound | Invalid parameter. 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 | The content to be detected is too large. Make sure the content is within the limits of the API. |
400 | InvalidParameter.Transfer | Failed to download or upload data. |
400 | InvalidParameter.Unsuitable | The data is empty or the parameter is invalid. |
400 | InvalidRamRole | You do not have RAM permissions. Contact the root account to grant you the AliyunVIAPIFullAccess permission. For more information, see Control access with RAM policies. |
400 | InvalidResult | Invalid parameter. Check the parameter value and the file content against the documentation. Check whether the image content is incomplete or too blurry. |
400 | InvalidSide | The specified parameter Side is not valid. Enter the correct Side parameter as described in the documentation. |
400 | InvalidTimeStamp.Expired | The difference between your local 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. Check whether the AccessKey ID and AccessKey secret are correct. |
400 | MissingImageURL | The image URL is missing. |
400 | MissingParameter | An input parameter is missing. |
400 | ParameterError | Invalid parameter. Check the parameter value. |
503 | ServiceUnavailable | The service is unavailable. If the server has returned a RequestID, contact us through the DingTalk group (23109592). |
400 | SignatureDoesNotMatch | The signature does not match. Check whether the AccessKey ID and AccessKey secret are correct. Check whether the signing method is correct. For more information, see Request signing. |
400 | SignatureNonceUsed | The SignatureNonce is a duplicate. The SignatureNonce for each request must be unique within 15 minutes. |
400 | Throttling | Throttling was triggered. For paid APIs, purchase a higher QPS. For free APIs, if you have 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, if you have 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 timed out. |
403 | Unauthorized | Insufficient RAM permissions. Grant the required permissions first. For more information, see Control access with RAM policies |
404 | InvalidImage.NotFoundFace | No face was found in the image. Check whether your image contains a face or if the face is too small. If a face is present, contact us through the DingTalk group (23109592). |
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 types of errors.
URL-related error codes
These error codes usually indicate that the file URL does not meet the requirements. For example, the URL is not secure or is 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, your 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. For example, a parameter is missing or has an incorrect type. Check whether your input parameters meet the requirements by referring to the request parameters table in the corresponding API document.
System service error codes
If this type of error occurs, resubmit the service request. If the problem persists, provide feedback in the DingTalk group (23109592).