tencent cloud

Tencent Cloud AI Digital Human

Product Overview
Overview
Product Features
Product Advantage
Purchase Guide
Pricing Guide
Purchase Guide
Process for Purchasing with Vouchers
Refund Instructions
Introduction of Avatar
Introduction to Image Categories
Basic Image Library
Guide on Avatar and Voice Clone
Digital Human Platform Operation Guide
Accessing Platform
Avatar Production and Asset Management
Digital Human Conversation Interaction Application and Management
Broadcast Digital Human Video Generation and Management
Operations Management and Analysis
Server API Integration
Digital Human API Access Mode Overview
Avatar aPaas API Calling Methods
Avatar Image Customization and Voice Clone API Documentation
Video Generation Service API Documentation
Interactive Digital Human Service API Documentation
Personal Asset Management API Documentation
Client SDK Integration
Overall Introduction
3D Client-Side Rendering SDK Integration
2D Client-Side Rendering SDK Integration
Digital Human SSML Markup Language Specification
Related Agreement
Privacy Policy
DSA (Data Sharing Agreement)
FAQs

Digital Human Video Production API Call Method

PDF
Focus Mode
Font Size
Last updated: 2025-12-19 15:33:53
This documentation primarily describes the API call methods on the Tencent Cloud AI Digital Human aPaaS platform, including permissions, common parameters, and signature requirements.

I. API Invocation Environment, Common Parameter and Signature Method

For details, please refer to digital human aPaas API calling method.

II. Permission Application and Activation

Video generation aPaas API usage permissions require purchasing related services before they are usable. For preliminary stage testing, contact the business manager to apply for a free trial quota.

III. Request and Response Structure

Request Body Structure
The request body is divided into Header and Payload. The Header can include RequestID to identify a single request for system issue tracking. Business parameters are placed in the Payload. Each API's input parameters in the product API documentation should be placed in the Payload for transmission.
{
"Header": {
"RequestID": "",
},
"Payload": {}
}
Response Body Structure
The response body is divided into two parameters: Header and Payload. The Header contains the result code, message, and the unique request ID which is the same as the value provided in the request body. The specific response parameters of the API will be placed in the Payload.
{
"Header": {
"Code": 0,
"Message": "",
"RequestID": "", // If not filled in during the request, it will be generated and returned by the cloud
},
"Payload": {}
}


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback