Queries the configuration of callbacks for video moderation results.

Usage notes

  • Obtain the main streaming domain, and then call this operation to query the configuration of callbacks for video moderation results.
  • Only some live centers support the automated review feature. For more information, see Supported regions.

QPS limit

You can call this operation up to 50 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. For more information, see QPS limit on an API operation in ApsaraVideo Live.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer automatically generates the sample code of the operation for different SDKs.

Request parameters

Parameter Type Required Example Description
Action String Yes DescribeLiveDetectNotifyConfig

The operation that you want to perform. Set the value to DescribeLiveDetectNotifyConfig.

DomainName String Yes example.com

The main streaming domain.

Response parameters

Parameter Type Example Description
RequestId String 16A96B9A-F203-4EC5-8E43-CB92E68F4CD8

The ID of the request.

LiveDetectNotifyConfig Object

The callback configuration.

DomainName String example.com

The main streaming domain.

NotifyUrl String http://aliyundoc.com

The callback URL.

Examples

Sample requests

http(s)://live.aliyuncs.com/?Action=DescribeLiveDetectNotifyConfig
&DomainName=example.com
&<Common request parameters>

Sample success responses

XML format

HTTP/1.1 200 OK
Content-Type:application/xml

<?xml version="1.0" encoding="UTF-8" ?>
<DescribeLiveDetectNotifyConfigResponse>
<RequestId>16A96B9A-F203-4EC5-8E43-CB92E68F4CD8</RequestId>
<LiveDetectNotifyConfig>
    <DomainName>example.com</DomainName>
    <NotifyUrl>http://aliyundoc.com</NotifyUrl>
</LiveDetectNotifyConfig>
</DescribeLiveDetectNotifyConfigResponse>

JSON format

HTTP/1.1 200 OK
Content-Type:application/json

{
  "DescribeLiveDetectNotifyConfigResponse" : {
    "RequestId" : "16A96B9A-F203-4EC5-8E43-CB92E68F4CD8",
    "LiveDetectNotifyConfig" : {
      "DomainName" : "example.com",
      "NotifyUrl" : "http://aliyundoc.com"
    }
  }
}

Error codes

HTTP status code Error code Error message Description
404 InvalidConfig.NotFound Config does not exist. The error message returned because the configuration is not found. Check whether the request parameters are valid.

For a list of error codes, see Service error codes.