Common error codes for video production
This topic describes the error codes that are returned by the server when a video production API request fails.
If you have questions about API integration, API calls, or other issues with the AI capabilities of the Alibaba Cloud Visual Intelligence API, you can contact us through the DingTalk group (23109592).
Troubleshooting center
You can use the Troubleshooting Center to diagnose API issues more efficiently.
Video production error codes
Status code | Error code | Description |
403 | AuthFailed | Authorization failed. Check the RAM permission configuration. |
400 | ClientError.IllegalArgument | Check the parameters. For example, check if the database represented by a 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 links that are not for OSS in the China (Shanghai) region, see Handle file URLs. |
500 | InternalError | An internal server error occurred. If your business is affected, contact us through the DingTalk group (23109592). |
500 | InternalError.Algo | An internal algorithm processing error occurred. If your business is affected, contact us through the DingTalk group (23109592). |
500 | InternalError.Busy | The algorithm service is busy. If your business is affected, contact us through the DingTalk group (23109592). |
500 | InternalError.Model | Failed to load the model. Retry later. If your business is affected, contact us through the DingTalk group (23109592). |
500 | InternalError.Timeout | The algorithm service timed out during internal processing. Retry later. If your business is affected, contact us through the DingTalk group (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 SDK. 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 go to the console, find the capability, and submit a request. You can call the capability only after the request is approved or you manually activate it. 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.Category | The category of the file content does not meet the requirements. |
400 | InvalidFile.Content | The data is empty or cannot be processed. |
400 | InvalidFile.Decode | The file cannot be decoded. |
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 file URL does not belong to the specified region. |
400 | InvalidFile.Resolution | The file resolution is invalid. |
400 | InvalidFile.Type | The file type is incorrect. Check the file type and use a type supported by the algorithm. For more information, see the API document for the algorithm. The Alibaba Cloud Visual Intelligence API reads the file to get its actual type instead of determining the type by the file extension. Checking only the file extension is not effective. For more information about how to determine and handle file types, see Determine and handle file types. |
400 | InvalidFile.Unsafe | The file link is not secure. |
400 | InvalidFile.URL | The file URL is invalid. |
400 | InvalidImage.Content | Check the image content based on the algorithm document. Replace the image with one that meets the algorithm 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 links 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 the URL before you pass 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 file links 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 resolution, and then 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 links 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. For more information, see the API document for the algorithm. |
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 | InvalidParameter | The request parameter is invalid. |
400 | InvalidParameter.BadRequest | A request parameter is missing or invalid. |
400 | InvalidParameter.Format | The format of a request parameter is incorrect. |
400 | InvalidParameter.NotFound | A parameter is incorrect. Check the parameter value based on the API document and the error message. Check if the parameter value contains leading or trailing spaces or other special characters. |
400 | InvalidParameter.TooLarge | A parameter is incorrect. The file size exceeds the limit. Adjust the file size based on the API document for the algorithm. |
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 based on the document. Check if the image content is incomplete or too blurry. |
400 | InvalidSide | The specified parameter Side is not valid. Enter a correct value for the Side parameter based on the document. |
400 | InvalidTimeStamp.Expired | The timestamp has expired. Update the timestamp. |
400 | MissingAccessKeyId | The AccessKey ID is not specified. Check if the AccessKey ID and AccessKey secret are correct. |
400 | MissingParameter | A request parameter is missing. |
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 (23109592). |
400 | SignatureDoesNotMatch | The signature is incorrect. Recalculate the signature. For more information, see Request signature. |
400 | SignatureNonceUsed | The signature nonce has 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 errors can occur. Consider both when handling the errors. |
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 errors can occur. Consider both when handling the errors. |
408 | Timeout | The request timed out. |
400 | 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. |
Common error codes
For more information about common API error codes, see the API Error Center.
Suggestions
If a service request returns an error code, refer to the error description to identify the cause and resolve the error. The following suggestions are provided for common error types.
URL-related error codes
These error codes usually indicate that the file URL is invalid. For example, the URL may be insecure or inaccessible. For more information, see Handle file URLs.
Image loading error codes
These errors are typically related to image 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 OSS, the bucket that you create in OSS must 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 are invalid. For example, a parameter may be missing or have an incorrect data type. To resolve these errors, verify that your input parameters meet the requirements that are described in the request parameters table of 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).