# User Access

All capabilities provided by the platform require authentication via APPID + AppKey before use. Therefore, please have your platform account ready before using the AIGC Video and Content Generation Platform. The platform account provides a callback URL configuration feature, which enables notification via user-provided APIs when long-running tasks are completed.

# Account Introduction

  • Account Activation

    • Currently, user accounts do not support self-registration. You can contact the operations team with your basic information (contact person / contact details / company information, etc.). The operations team will create your account and configure the relevant settings.

  • Obtaining Account Information

    • User account information consists of two parts: basic information and resource configuration. You can retrieve the latest information in real-time through the API endpoints we provide.
      • Basic Information: Includes account ID, company name, service validity start and end dates, as well as APPID and AppKey information.
      • Resource Configuration: Includes total available quota for avatar model generation, total used quota for avatar model generation, total available quota for TTS personal voice model generation, total used quota for TTS personal voice model generation, total available video generation duration, total used video generation duration, maximum concurrent task quota for avatar model generation (total available), maximum concurrent task quota for avatar model generation (total used), maximum concurrent task quota for TTS personal voice model generation (total available), maximum concurrent task quota for TTS personal voice model generation (total used), maximum concurrent task quota for video generation (total available), maximum concurrent task quota for video generation (total used), and other information.

  • User Authentication

    • The platform provides an interface for various systems to obtain tokens during identity verification. User authentication is completed through a signature generated by encrypting the appId, timestamp, and appKey. Once authentication is passed, the related services can be used.
    • To call all platform API services, users need to access the service endpoint: aigc.softsugar.com, and include the token information in the request header (the token is a signature generated by encrypting appId + timestamp + appKey [MD5(appId + timestamp + appKey)], with the MD5 result taken as a 32-character lowercase value. All subsequent API calls require this token, added as Header: Authorization: Bearer {token}).

# API Documentation

# Third-Party System Access Login

# API Description

This interface is used for various systems to obtain tokens during identity verification. The signature is generated by encrypting appId, timestamp, and appKey [MD5(appId + timestamp + appKey)], with the MD5 result taken as a 32-character lowercase value. All HTTP API calls require this token, added as Header: Authorization: Bearer {token}. All WebSocket API calls require this token, added as Header: Authorization: Bearer {token} or appended to the URL. The token passed in the Header takes higher priority.

# Request URL

POST /api/uc/v1/access/api/token

# Request Header

Content-Type: application/json

# Request Parameters

JSON array format. The field definitions for objects in the array are as follows:

Field Type Required Description
appId String True App ID (ID used for user access authentication)
timestamp String True Current timestamp, accurate to milliseconds
sign String True Generated signature (the MD5 computed value converted to a hexadecimal string; note that if any byte's converted length is insufficient, pad with leading zeros)
grantType String True Authentication type (fixed value 'sign')

# Request Example

{
  "appId": "ID",
  "timestamp": "1676797061518",
  "sign": "c4b08ca7d242939b8bf9c1dbb1a1911a",
  "grantType": "sign"
}

# Response Elements

Field Type Required Description
code Integer True 0 - Success, other - Error
message String True Detailed error information
data Object True Data object, returns null on error
  - permissions Object[] True Permission object array
  - roles Object[] True Role object array
  - accessToken String True Access token, default validity 8 hours; multiple requests within validity period return the same token
  - expiresIn Integer True Remaining lifetime of the access token, unit: seconds
  - refreshToken String True Refresh Token
  - refreshTokenExpiresIn Integer True Remaining lifetime of the refresh token, unit: seconds
  - user Object True User object information

permissions

Field Type Required Description
id Long True Permission ID
appId Long True System application ID
resourceId Integer True Resource ID
action Integer True Permission type (0: All, 1: Create, 2: Modify, 3: Delete, 4: Query)
creator Long True Creator ID
createTime String True Creation time, yyyy-MM-dd HH:mm:ss

roles

Field Type Required Description
id Long True Role ID
roleName String True Role name
appId Long True System application ID
description String False Description
isDelete Integer True Deletion flag (0: Not deleted; 1: Deleted)
creator Long True Creator ID
createTime String True Creation time, yyyy-MM-dd HH:mm:ss
updater Long True Updater ID
updateTime String True Update time, yyyy-MM-dd HH:mm:ss

user

Field Type Required Description
id Long True User ID
userName String True User name
profilePhoto String False Profile photo
company String False Company name
companyPhone String False Company phone
companyContact String False Company contact address
status Integer True Account status (0: Not activated; 1: Enabled; 2: Disabled)
effectiveBeginDate Date True Effective start date, yyyy-MM-dd HH:mm:ss
effectiveEndDate Date True Effective end date, yyyy-MM-dd HH:mm:ss
extraInfo String False Additional information
description String False Description
appId String True App ID
appKey String True App Key
licensePath String False License path
isDelete Integer True Deletion flag (0: Not deleted; 1: Deleted)
creator Long True Creator ID
createTime String True Creation time, yyyy-MM-dd HH:mm:ss
updater Long True Updater ID
updateTime String True Update time, yyyy-MM-dd HH:mm:ss

# Response Example

{
    "code": 0,
    "message": "success",
    "data": {
        "permissions": [
            {
                "id": 1,
                "appId": "Virtual Human Application",
                "resourceId": 1,
                "action": null,
                "creator": 1,
                "createTime": "2022-05-23 15:12:35"
            }
        ],
        "roles": [
            {
                "id": 3,
                "roleName": "Enterprise",
                "appId": 1,
                "description": null,
                "isDelete": 0,
                "creator": 1,
                "createTime": "2022-05-23 15:12:35",
                "updater": 1,
                "updateTime": "2022-05-23 15:12:35"
            }
        ],
        "accessToken": "ZGI3YzRiZmY4ZmFjMjM2MDExODUxNDdmY2MwNGY4OTA0NGRmNGNjYi1jNGNmLTRlMTEtOTExOC05YTU0YTM2NjFjODY",
        "user": {
            "id": 4,
            "userName": "Enterprise1",
            "profilePhoto": null,
            "company": null,
            "companyPhone": null,
            "companyContact": null,
            "status": 1,
            "effectiveBeginDate": null,
            "effectiveEndDate": null,
            "extraInfo": null,
            "description": null,
            "appId": null,
            "appKey": null,
            "licensePath": null,
            "isDelete": 0,
            "creator": 1,
            "createTime": "2022-05-23 15:13:03",
            "updater": 1,
            "updateTime": "2022-05-24 14:26:05"
        }
    }
}

# User Token Refresh

# API Description

Actively refresh the user's Access Token to obtain a new Access Token and Refresh Token, and recalculate the Access Token validity period. Note: When calling this interface, the Authorization parameter value should be the Refresh Token. The minimum interval between two consecutive token refresh calls must not be less than 3 hours; otherwise, the message "refresh token too frequent, limited to 3-hour intervals" will be returned.

# Request URL

POST /api/uc/v1/access/api/token/refresh

# Request Header

Content-Type: application/json Header: Authorization: Bearer {refresh token}

# Request Parameters

Field Type Required Description
appId String True App ID (ID used for user access authentication)
grantType String True Authentication type (fixed value 'refreshToken')

# Request Example

{
  "appId": "APP ID",
  "grantType": "refreshToken"
}

# Response Elements

Field Type Required Description
code Integer True 0 - Success, other - Error
message String True Detailed error information
data Object False Data object, returns null on error
  - accessToken String True Access token, default validity 8 hours
  - expiresIn Integer True Remaining lifetime of the access token, unit: seconds
  - refreshToken String True Refresh Token
  - refreshTokenExpiresIn Integer True Remaining lifetime of the refresh token, unit: seconds

# User Logout

# API Description

Cleans up cache information when the user logs out of the system.

# Request URL

POST /api/uc/v1/web/logout

# Request Header

Content-Type: application/json

# Request Parameters

None

# Request Example

None

# Response Elements

Field Type Required Description
code Integer True 0 - Success, other - Error
message String True Detailed error information
data Object False Success or failure; returns 1 on success, 0 or null on error

# Response Example

{
    "code": 0,
    "message": "success",
    "data": 1
}

# Get Account Basic Information and Resource Configuration

# API Description

When an administrator creates an account, a series of basic information and resource configuration details are filled in. This information is available for users to retrieve. This interface retrieves account basic information, resource configuration, and usage status by account ID.

# Request URL

GET /api/2dvh/v1/user/config/resource?userId={userId}

# Request Header

Content-Type: application/x-www-form-urlencode

# Request Parameters

Field Type Required Description
userId Long True Account ID

# Request Example

https://xxx.softsugar.com/api/2dvh/v1/user/config/resource?userId=2

# Response Elements

Field Type Required Description
code Integer True 0 - Success, other - Error
message String True Detailed error information
data Object False Data object, returns null on error
  - basicInfo Object True Account basic information
  - resourceConfig Object True Account resource configuration and usage info

Basic Information

Field Type Required Description
id Integer True ID
company String True Company name
effectiveBeginDate Date True Service validity start date, yyyy-MM-dd HH:mm:ss
effectiveEndDate Date True Service validity end date, yyyy-MM-dd HH:mm:ss
appId String True APP ID (ID used for user access authentication)
appKey String True APP Key

Resource Configuration and Usage Information

Field Type Required Description
id Long True ID
genCharModelTotalQty Integer True Total available quota for avatar model generation
genCharModelUsageQty Integer True Total used quota for avatar model generation
genTtsCharVoiceModelTotalQty Integer True Total available quota for TTS personal voice model generation
genTtsCharVoiceModelUsageQty Integer True Total used quota for TTS personal voice model generation
genVideoDurationTotalQty Integer True Total available video generation duration
genVideoDurationUsageQty Integer True Total used video generation duration
charModelMaxConTasksTotalQty Integer True Total available max concurrent tasks for avatar model generation
charModelMaxConTasksUsageQty Integer True Total used max concurrent tasks for avatar model generation
ttsCharVoiceModelMaxConTasksTotalQty Integer True Total available max concurrent tasks for TTS voice model generation
ttsCharVoiceModelMaxConTasksUsageQty Integer True Total used max concurrent tasks for TTS voice model generation
videoGenMaxConTasksTotalQty Integer True Total available max concurrent tasks for video generation
videoGenMaxConTasksUsageQty Integer True Total used max concurrent tasks for video generation

# Response Example

{
    "code": 0,
    "message": "success",
    "data": {
        "resourceConfig": {
            "id": 1,
            "company": "zhangsan",
            "effectiveBeginDate": "2019-01-01 20:20:20",
            "effectiveEndDate": "2019-01-01 20:20:20",
            "appId": "7sadf7sadf7ads7f7asf7sda7f",
            "appKey": "7sadf7sadf7ads7f7asf7sda7f"
        },
        "resourceConfig": {
            "id": 1,
            "genCharModelTotalQty": 12,
            "genCharModelUsageQty": 2,
            "genTtsCharVoiceModelTotalQty": 12,
            "genTtsCharVoiceModelUsageQty": 2,
            "genVideoDurationTotalQty": 21,
            "genVideoDurationUsageQty": 11,
            "charModelMaxConTasksTotalQty": 12,
            "charModelMaxConTasksUsageQty": 3,
            "ttsCharVoiceModelMaxConTasksTotalQty": 11,
            "ttsCharVoiceModelMaxConTasksUsageQty": 4,
            "videoGenMaxConTasksTotalQty": 11,
            "videoGenMaxConTasksUsageQty": 7
        }
    }
}

# Common Data Structures and Platform Specifications

# Service Endpoint

Region Public Access Address VPC Access Address
East China aigc.softsugar.com

# Avatar Model Video Collection Specifications

To perfectly clone an avatar, please follow the SenseTime Digital Human Collection and Production Specifications during recording. The content includes video and audio, used for 2D digital human training and testing. For details, refer to: Collection Specifications (opens new window) and Video Material Self-Inspection Checklist (opens new window).

For premium digital human video collection, please refer to: Premium Digital Human Collection Guide (opens new window).

# Video Synthesis Parameter Input Specifications

Creating a video synthesis task requires passing in correct param information, which includes various video synthesis parameters (the parameter is a JSON-escaped string). Please refer to Parameter Description and JSON Examples and Example Output (opens new window).

# Live Streaming Parameter Input Specifications

Creating a live streaming task requires passing in correct param information, which includes various parameters (the parameter is a JSON-escaped string). Please refer to Live Streaming Script JSON Definition and Examples and Live Streaming Takeover JSON Definition and Examples.

# Web-JS Code Examples

To help web-based customers more easily understand the integration and usage of the APIs, we provide web-JS code examples for some functional modules, including: live streaming creation, live streaming takeover, live streaming shutdown, creating avatar model generation/update tasks and querying task status, creating video synthesis tasks and querying task status, creating TTS voice model generation tasks and querying task status, etc. For details, please refer to Code Examples (opens new window).

# Common Response Parameters

All interfaces return data in the following structure. Specific business content is returned in the data field.

Field Type Required Description
code Integer True Status code
message String True Error message
data Object False Response data

# Pagination Information

Field Type Required Description
pageNo Integer True Current page number
numberPages Integer True Total number of pages
numberRecords Integer True Total number of records
pageSize Integer True Number of records per page
startIndex Integer True Start index of the current page
nextPageToken String False Next page token

# HTTP Callback Event Notification

This section describes the callback mechanism, usage process, and authentication principles for HTTP callback event notifications.

# HTTP Callback Mechanism

You need to deploy an HTTP service to receive callback messages and provide a callback URL, which the platform will configure accordingly. When an event occurs, the PAAS server will send an HTTP POST request to the URL, with the event notification content delivered through the HTTP Body. Your HTTP service performs signature authentication on the HTTP POST request. If authentication succeeds and the response status code is 200, the callback is considered successful. If any other status code is returned or the response times out, the callback is considered failed. For the authentication principle, see HTTP Callback Authentication Principle. After a successful callback, the configured callback URL will receive the corresponding event notification content. After a failed callback, the platform will retry the callback 2 more times, for a maximum total of 3 attempts. After 3 failed attempts, the callback event notification will be discarded.

# HTTP Callback Authentication Principle

The PAAS service supports adding a specific signature header during HTTP (including HTTPS) callbacks for the callback message receiving server to perform signature authentication, preventing illegal or invalid requests.

# Notes

Whether to enable HTTP callback authentication is at your discretion (it is recommended to enable it). Once an AuthKey (authentication key) is set, all authentication-related content will be included in the callback for the callback message receiving server to use for authentication. Setting an AuthKey does not affect existing functionality; whether to verify is at your discretion. If no AuthKey is set, there will be no impact.

# Authentication Parameters

The specific authentication parameters added to the callback HTTP message body are as follows:

Field Type Required Description
timestamp Integer False UNIX timestamp, positive integer, fixed length of 10, seconds since January 1, 1970, representing the time the callback request was initiated.
signature String False Signature string, a 32-character lowercase MD5 value. See the signature algorithm below for details. (The MD5 computed value converted to a hexadecimal string; note that if any byte's converted length is insufficient, pad with leading zeros)

# Signature Algorithm

The calculation of signature depends on the following fields:

Field Example Description
Callback URL https://www.example.com/your/callback The callback address configured by the user.
timestamp 1693206851 UNIX timestamp, positive integer, fixed length of 10, seconds since January 1, 1970, representing the callback request time.
AuthKey abcde1231693206851 The authentication key provided by the user, 16-32 characters, must contain uppercase letters, lowercase letters, and numbers.

Concatenate the above three fields and calculate the MD5 value:

MD5Content = CallbackURL + timestamp + AuthKey
signature = md5sum(MD5Content)

Example of signature calculation:

signature = md5sum(https://www.example.com/your/callback1693206851abc123) = 863151b586912152aacee3124f81e301

# Callback Message Receiving Server Verification Rules

  • The callback message receiver concatenates the configured callback URL, timestamp, and AuthKey string, calculates the MD5 value to obtain an encrypted string, and compares it with the signature field. If they do not match, the request is considered illegal.
  • The callback message receiver obtains the current time and subtracts the timestamp field from the callback request. If the difference exceeds the specified time set by the callback message receiving server (e.g., 5 minutes, defined by the receiving server), the request is considered invalid.

# AuthKey Rotation

When rotating AuthKeys, to ensure the callback functionality is not affected, the callback message receiving server needs to support a smooth transition between the old and new AuthKeys, i.e., supporting authentication with both the old and new AuthKeys during a transition period, handled by the callback message receiving server.

The recommended operation sequence is as follows:

  1. Define a new AuthKey.
  2. Upgrade the callback message receiving server to support authentication with both the new and old AuthKeys.
  3. Update the AuthKey to the new one in the control console.
  4. After observing for a period, remove the support for the old AuthKey from the callback message receiving server.
  5. Rotation complete.

# HTTP Callback Usage

# Prerequisites

  • You have deployed an HTTP/HTTPS service for receiving callback messages.

# Error Code Descriptions

Error Code Description
0 Success
400 Error
500 Error
10101001 IAM identity ID is invalid.
10999999 Access center exception
20999999 Generation platform exception
30999999 Digital asset platform exception
50101503 Authorization parsing error
50101504 Authorization does not exist
50102101 Phone number cannot be empty
50102102 Phone number is invalid, must be a valid 11-digit phone number
50102103 Verification code cannot be empty
50102104 Verification code is invalid
50102105 Verification code has expired
50102106 Account name cannot be empty
50102107 Account name is invalid, must be a valid email or phone number
50102108 Password cannot be empty
50102109 Account or password is incorrect
50102110 User name cannot be empty
50102111 Company information cannot be empty
50102112 Email cannot be empty
50102113 Password must use at least two types of the following: letters, numbers, and symbols, 6-16 characters, case-sensitive
50102114 User name maximum length is 25 characters
50102115 Company information maximum length is 50 characters
50102116 Email maximum length is 80 characters
50102117 Passwords do not match
50102118 Failed to send verification code
50102119 Email address rules: digits, letters, underscores + @ + digits, letters + . + letters (length 2-4)
50102120 Error modifying password
50102121 Failed to create account
50102122 Failed to retrieve account information
50102123 Invalid verification code type
50102124 Email already exists
50102125 Account ID must be greater than 0
50103201 Order does not exist
50103202 To restore an order on the enterprise side, the current status must be Cancelled
50103203 Not deleted by an administrator on the admin side
50103204 To delete an order, the current status must be Cancelled
50103205 To cancel an order, the current status must be Urged/Pending/In Progress
50103206 To urge an order, the current status must be Urged/Pending/In Progress
50103207 The above effects have been discontinued and cannot generate orders. Please clear and reorder
50103208 The number of effects included in the generated order cannot be 0
50103209 Cannot re-urge within 24 hours
50103210 Only administrators can perform this operation
50103211 Deleted orders cannot have their status modified
50103212 Administrators cannot view cancelled orders
50103213 Only administrators can view order details
50103214 Administrators cannot create orders
50103215 Invalid order status
50103216 Invalid order sort name
50103217 Only enterprise accounts can urge orders
50103218 Only enterprise accounts can cancel orders
50104401 Effect tag has associated effects
50104402 Duplicate effect tag name
50105301 File key / validity time is invalid
50105302 File upload failed
50105303 File download failed
50105304 File deletion failed
50105305 Input stream not obtained
50105306 S3 file does not exist
50105307 S3 file compression exception
50106403 Effect package decompression exception
50106404 Effect package parsing exception
50106405 Effect package encryption exception
50106406 Effect package JSON file does not exist
50106407 Effect is in use and cannot be deleted
50106703 Invalid sort name
50107601 Invalid app_id
50107603 Invalid signature
50107604 Illegal data format
50107607 Data decryption failed
50107605 APP key not found
50107606 SDK key not found
60102101 Phone number cannot be empty
60102102 Phone number is invalid, must be a valid 11-digit phone number
60102103 Verification code cannot be empty
60102108 Password cannot be empty
60102112 Email cannot be empty
60102116 Email maximum length is 80 characters
60102119 Email address rules: digits, letters, underscores + @ + digits, letters + . + letters (length 2-4)
60102123 Invalid verification code type
60102124 Email already exists
60102126 Account does not exist
60102127 Please enter an email or phone number
60102128 Account pending activation
60102129 This account has been disabled. To use it, please contact the administrator to enable the account
60102130 Failed to log in %s consecutive times, please try again after %s
60102131 RSA key pair generation exception
60102132 Key pair generation failed!
60102133 Public key cannot be empty
60102134 RSA private key retrieval exception
60102135 Public key has expired, please regenerate
60102136 Decryption error occurred
60102137 RSA decryption exception
60102138 Incorrect password
60102139 Phone number already exists
60102140 Abnormal user status
60102141 Role already exists
60102142 User-role relationship already exists
60102143 Role-permission relationship already exists
60102144 Failed to send email to %s
60102145 Service validity period is unreasonable
60102146 No permission for the business corresponding to this parameter (please verify whether the user exists, whether user parameters conflict, whether the status is normal, whether role relationship data is reasonable, etc.)
60102147 Number of new roles must be greater than 0
60102148 Number of export roles must be greater than 0
60102149 Service validity start date cannot be empty
60102150 Service validity end date cannot be empty
60102151 appId cannot be empty
60102152 appKey cannot be empty
60102153 New password cannot be empty
60102154 No role bound under this application
60102155 Number of new roles and export roles cannot be empty
60102156 Account is not within the validity period
60102157 appId already exists
60102158 appId and appKey do not match
60102159 Please enter a contact name of 2-8 characters in Chinese or English
60111101 APP does not exist
60111301 APP does not exist
60112505 Access authorization has expired, please log in again
60112160 Third-party system signature verification failed
60112161 Refresh token too frequent, limited to %s hour intervals
60112162 Grant type is invalid
70107701 Tag is in use
70107702 System tags cannot be modified or deleted
70104703 Tag name cannot be empty
70104704 Tag type cannot be empty
80107807 Current algorithm status prohibits restart
80107811 Virtual human service request exception
80108801 OPEN FEIGN request source is invalid
80108802 No online algorithm worker node instances in the registry
80108803 This algorithm worker node instance is not in online status in the registry
80108804 No algorithm worker node instances in the registry
80108805 Algorithm worker node instance negotiation failed
80108806 Algorithm scheduling service failed to get cartoon style collection from virtual human service interface
80108810 Algorithm scheduling service failed to get cartoon style and download URL collection from virtual human service interface
80109809 No available idle task resources on worker nodes for scheduling, please try again later
80109814 Scheduling command does not exist
80109815 Algorithm service request exception
80109817 Dispatcher does not support the worker's algorithm
80109833 Current algorithm task has abnormal status in the scheduling center
80117823 Load value is invalid or empty.
80117824 No worker using this GAN algorithm category.
80117825 This feature is not registered in the commercial service.
80117826 Error pulling full category feature configuration.
80117827 Feature-zip mapping does not exist.
80115947 Current service resources have reached the limit, cannot create live stream, please try again later
80115950 No historical parameter records, update not supported, model needs to be regenerated
80115962 Your trial account live streaming has reached the usage limit: %s channels, no available resources, please try again later
80115963 Your production account live streaming has reached the usage limit: %s channels, no available resources, please try again later
80115964 Live streaming service has reached the available resource limit, no available resources, please try again later
80115983 The number of created %s tasks has reached the account's concurrent task limit, please try again later
81107808 Algorithm worker node does not support the created thread type
81114812 Virtual human cartoon avatar SDK failed to create avatar
81114813 Virtual human cartoon avatar SDK handler resources exhausted, please try again later
81114816 Style not found
81117819 Bling SDK failed to create GAN effect handle
81117820 Image size cannot exceed 5MB
81117821 SDK task is running
81117822 Function value is invalid.
81117828 Attribute editing feature-zip mapping configuration does not exist.
81118829 AvatarPackage Handler exception
81118830 AvatarPackage Handler creation exception, error code
81118831 AvatarPackage Handler license verification failed, error code
81118832 AvatarPackage Handler process failed, error code
81118836 AvatarPackage FBX compression not supported
81118837 AvatarPackage JSON format exception
81118838 Material file missing required file types, cannot generate avatar FBX/GLB file
81118839 AvatarPackage Handler processing, please try again later
82116818 Task ID cannot be empty
83119834 No idle video generation worker available
83119308 File decompression exception
83115905 Account ID cannot be empty
83115906 Failed to start 2D digital human algorithm task
84115913 Video generation avatar model format error, must be in zip format and contain assets and models resources
84115914 Video task stylization data input format is invalid, only supported video formats: mp4/csv/vid/ebm/mov, image formats: jpg/JPG/jpeg/JPEG/png/bmp
83115920 Failed to start 2D digital human live streaming algorithm task
83115921 Failed to stop 2D digital human live streaming algorithm task
83115922 Failed to initialize 2D digital human live streaming algorithm task
83115923 Failed to take over 2D digital human live streaming algorithm task
83115924 Live streaming video generation avatar model format error, must be in zip format and contain assets and models resources
83115951 File format in background/foreground URL does not meet type requirements, 0(jpg,jpeg,png,gif,bmp,tiff,svg), 1(mp4,avi,mov,wmv,flv,mkv)
83115952 Initialization failed
83115961 urtcUid must be a pure numeric value not exceeding 32-bit uint length
83115965 When urtcUseExternalApp is true, urtcToken, urtcAppId, urtcChannelId, and urtcUid are required
83115971 Live streaming takeover list reordering failed
83115972 Failed to retrieve live streaming takeover list
83115973 Failed to join live streaming list
83115977 Live streaming takeover is initializing, reordering not supported
84115912 Cannot generate avatar model task when used quota for avatar model generation exceeds total quota
84115915 Live streaming initialization not yet complete, please wait
84115916 Live stream is already started, please do not start again
84115917 Live streaming task exception, cannot start
84115918 Live streaming task is not in progress, cannot take over
84115919 Live streaming task has completed or has abnormal status, no need to close
84999920 Please follow these parameter rules: assetScale is optional, default value is 1.0, range is 0.1 to 3; assetStart and assetEnd are optional and must appear as a pair, both cannot be negative, assetEnd must be greater than assetStart; greenParamsSpillByalpha range is 0.3 to 0.7, greenParamsBlurKs must be >= 1 and odd
84115921 Current live streaming takeover exception
84115922 Current live stream is being taken over, please try again later
84115923 Current live stream has been closed, cannot start
84115925 Current user does not have permission to perform this operation
84115926 Connection lost for more than 10 minutes, please reconnect
84115927 Invalid request parameters
84115928 Invalid resource path
84115929 Task/session does not exist
84115930 Live stream is in progress
84115931 Takeover error, unknown reason
84115932 Viewable live stream statuses are: 5 (Completed), 9 (Abnormal)
84115933 Live stream has started, channel ID is %s
84115934 Live stream initialization complete, channel ID is %s
84115940 Failed to create TTS personal voice model generation task
84115941 Failed to cancel TTS personal voice model generation task
84115942 Failed to get TTS personal voice model task details
84115935 Video generation JSON file parsing error
84115943 Token is invalid
84115945 Live streaming initialization JSON file parsing error
84115944 Cannot create new live streaming task when used live streaming duration exceeds total quota
84115946 Live stream has been closed, cannot proceed with further operations
84115948 Current remaining allocatable channels are %s (total - public reserved - sum of allocated). Please adjust. When configured count > total available, system resources will be preempted!
84115949 Only tasks in waiting or in-progress status can be cancelled
84115955 Refreshing rtcToken too frequently, limited to %s hour intervals
84115956 This channelId does not exist in the current live streaming session
84115953 Live stream has been closed
84115957 This account has an active live streaming task. To avoid abnormal impact, account tag changes are temporarily not supported
84115958 Cannot generate TTS model task when used TTS model generation quota exceeds total quota
84115959 Avatar model file URL is invalid, or is not in zip format
84115960 Live streaming push JSON file parsing error
84115966 Only cancelled or abnormal tasks can be regenerated
84115967 Duplicate task %s found in billing details
84115968 Failed to acquire lock %s.
84115969 Task does not exist or status does not meet requirements
84115970 Administrators cannot create tasks
84115974 Failed to change TTS personal voice model priority task
84115975 The number of generated 2K avatar models has reached the account's total available quota limit, cannot create task
84115976 The number of generated 4K avatar models has reached the account's total available quota limit, cannot create task
84115975 The number of generated 2K avatar models has reached the account's total available quota limit, cannot create task
84115976 The number of generated 4K avatar models has reached the account's total available quota limit, cannot create task
84115979 The number of created voice cloning tasks has reached the account's concurrent task limit, please try again later
84115980 NLP APP does not exist
84115981 NLP Skill does not exist
84115982 Task concurrency limit must be greater than 0
84115984 Found %s records, data volume is large, please export and view.
89999998 Request rate limit key cannot be empty
89999999 Your access is too frequent, please try again later
90113801 This user has reached the maximum number of character creations
90113802 This user has reached the maximum number of character exports
90113803 Character creation count verification exception
90113804 Raw material retrieval exception
90113805 Temporary folder deletion exception
90113806 Character generation exception, please check the uploaded image according to requirements or try again later
90113807 No available Handler
90113808 JSON file update exception
90113809 Algorithm returned failure
90113810 SDK Aimodel file path does not exist
90113811 Please check and upload a correct face image, then try regenerating
90113812 Unsupported image format
90113813 Loading failed due to incorrect file format
90113815 Please check the auto face-sculpting model configuration for this character style
90114814 Only jpg/png format images are supported
90114833 Character does not exist
90114834 Updates too frequent, please try again later
90114835 File content cannot be parsed, please refer to system-generated character material files
90115901 Priority execution task failed
90115903 Failed to start hyper-realistic algorithm task
90115904 Failed to stop hyper-realistic algorithm task
99999990 Access forbidden
99999991 Service unavailable
99999992 Hystrix bad request
99999993 Hystrix runtime exception
99999994 Hystrix timeout
99999995 Feign error
99999996 Invalid input
99999997 Gateway error
99999998 External service error
99999999 Error

The above covers the preparation work required for users to access and use the platform services.

Last Updated: 4/10/2026, 3:13:22 PM

← Platform Capabilities →