Adds an audio moderation configuration.
Operation description
- The content moderation feature detects undesirable sensitive content in the audio from live streams and returns callbacks to notify you of the violations. Then, you can manually review the content and take actions accordingly.
- Only some live centers support the content moderation feature. For more information, see Supported regions.
QPS limit
You can call this operation up to 10 times per second per account. Requests that exceed this limit are dropped and you will experience service interruptions. We recommend that you take note of this limit when you call this operation.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resourcesis used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| live:AddLiveAudioAuditConfig | create | *Domain acs:cdn:*:{#accountId}:domain/{#DomainName} |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| DomainName | string | Yes | The main streaming domain. | example.com |
| AppName | string | Yes | The name of the application to which the live stream belongs. The value of this parameter must be the same as the application name in the ingest URL. Otherwise, the configuration does not take effect. The application name is case-sensitive. | liveApp**** |
| StreamName | string | Yes | The name of the live stream. The value of this parameter must be the same as the stream name in the ingest URL. Otherwise, the configuration does not take effect. The stream name is case-sensitive. | liveStream**** |
| OssBucket | string | No | The name of the OSS bucket in which the recording is stored. | liveBucket**** |
| OssEndpoint | string | No | The endpoint of OSS. | cn-oss-****.aliyuncs.com |
| OssObject | string | No | The name of the recording stored in OSS. | liveObject**** |
| BizType | string | No | The business type. You can specify a model. The default value is the domain name. | example.edu |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "7BF95F2A-3B24-4CDE-9346-7F6FA86697A1"
}Error codes
| HTTP status code | Error code | Error message |
|---|---|---|
| 400 | MalformedParam | %s |
| 400 | MissingParam | %s |
| 400 | ConfigExisted | %s |
| 400 | ConfigNotFound | %s |
| 500 | InternalError | %s |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|