UpdateLiveRecordNotifyConfig - ApsaraVideo Live

Usage notes

You can call this operation to modify the following settings:

The callback URL that is used to receive notifications about recording events and status. For more information, see Recording event callbacks.
The callback URL for on-demand recordings. For more information, see On-demand recording callbacks.
The setting that specifies whether to enable callbacks for recording status.

QPS limit

You can call this operation up to 30 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 limits.

Debugging

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

Request parameters

Parameter	Type	Required	Example	Description
Action	String	Yes	UpdateLiveRecordNotifyConfig	The operation that you want to perform. Set the value to UpdateLiveRecordNotifyConfig.
DomainName	String	Yes	example.com	The main streaming domain.
NotifyUrl	String	Yes	http://learn.aliyundoc.com/examplecallback.action	The callback URL that is used to receive notifications about recording events and status. Note The URL must start with `http://` or `https://`. You must use URLEncoder for encoding. This way, the system can identify Chinese characters, spaces, and special characters.
OnDemandUrl	String	No	http://guide.aliyundoc.com/ondemandcallback.action	The callback URL for on-demand recordings. Note The URL must start with `http://` or `https://`. You must use URLEncoder for encoding. This way, the system can identify Chinese characters, spaces, and special characters.
NeedStatusNotify	Boolean	No	false	Specifies whether to enable callbacks for recording status. Valid values: true false (default)

Response parameters

Parameter	Type	Example	Description
RequestId	String	16A96B9A-F203-4EC5-8E43-CB92E68F4CD	The request ID.

Examples

Sample requests

http(s)://live.aliyuncs.com/?Action=UpdateLiveRecordNotifyConfig
&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" ?>
<UpdateLiveRecordNotifyConfigResponse>
	<RequestId>16A96B9A-F203-4EC5-8E43-CB92E68F4CD8</RequestId>
</UpdateLiveRecordNotifyConfigResponse>

JSON format

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

{
  "UpdateLiveRecordNotifyConfigResponse" : {
    "RequestId" : "16A96B9A-F203-4EC5-8E43-CB92E68F4CD8"
  }
}

Error codes

HTTP status code	Error code	Error message	Description
400	InvalidNotifyUrl.Malformed	Specified NotifyUrl is invalid.	The error message returned because the callback URL is invalid. Check whether the value of the NotifyUrl parameter is valid.
400	InvalidNotifyUrl.Unsafe	Specified NotifyUrl is not safe.	The error message returned because the callback URL is unsecure. Check whether the value of the NotifyUrl parameter is valid.
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.