Overview
Product Features
Product Advantage
Interface Integration FAQs
Serial number | Problem description | Solutions | Remarks |
1 | Authentication failure occurs when the interface is called. | 1. Ensure that the parameters are sorted in alphabetical order when generating the signature. 2. Ensure that the timestamp parameter is set to the current time. 3. See the example parameters on the right. Do the calculation according to your own signature steps, and when your result matches the example, it means that the signature calculation steps are correct. | The parameters are described as follows: appkey = e38267c0e86411ebb02aed82acb0ed99 accesstoken = f68f2d10ae9e4604b76fb05cf46bccec timestamp=1646636485 Signature result: fWuaC9kmaicCggXc693uK%2BsZQ8qe88O4HVQNTdwZuo%3D |
2 | A "miss Content Length" error occurs when the interface is called. | 1. Check if the request body includes the header parameters and payload parameters; there is an error without them, as shown in the example on the right. 2. The parameter types must be filled in strictly according to the interface documentation. 3. Check if the URL is spelled correctly. |  |
3 | UnauthorizedOperation: unauthorized operation: No project was created for this appkey. | The customer has not been granted permission to use the image customized interface. Please contact Tencent personnel for permission. | |
4 | Do video materials need to be uploaded to the customer's Tencent Cloud COS? | Not required. Video materials will be sent to the Avatar's internal COS via a temporary token, so there is no need for the customer to activate Tencent Cloud COS. | |
5 | How to obtain the Bucket, Region, and Key when the COS SDK is called? | These can be parsed from the prefix, as shown in the example on the right. |  |
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback