Creates a recording callback configuration for a streaming domain.
Operation description
Check the live recording callback configuration before calling this interface to add the domain-level recording callback configuration. To query live recording callback configuration, see DescribeLiveRecordNotifyConfig
QPS limit
A single user can perform a maximum of 30 queries per second (QPS). Throttling is triggered when the number of calls per second exceeds the QPS limit. The throttling may affect your business. Thus, we recommend that you observe the QPS limit on this operation. For more information about what a single user means and the QPS details, see QPS limit on an API operation in ApsaraVideo Live.
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:AddLiveRecordNotifyConfig | create | *Domain acs:cdn:*:{#accountId}:domain/{#DomainName} |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| DomainName | string | Yes | The main streaming domain. | example.com |
| NotifyUrl | string | Yes | The callback URL that is used to receive notifications about recording events and status. The URL must start with | http://demo.aliyundoc.com/examplecallback.action |
| NeedStatusNotify | boolean | No | Specifies whether to enable callbacks for recording status. Valid values:
| false |
| OnDemandUrl | string | No | The callback URL for on-demand recordings. The URL must start with | http://learn.aliyundoc.com/ondemandcallback.action |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "16A96B9A-F203-4EC5-8E43-CB92E68F4CD8"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | InvalidNotifyUrl.Malformed | Specified NotifyUrl is invalid. | Invalid value of notifyurl. Check whether the notifyurl parameter that you specified is correct. |
| 400 | InvalidNotifyUrl.Unsafe | Specified NotifyUrl is not safe. | Invalid value of notifyurl. Check whether the notifyurl parameter that you specified is correct. |
| 400 | ConfigAlreadyExists | Config has already exist. | - |
| 400 | InvalidOnDemandUrl.Malformed | Specified OnDemandUrl is invalid. | - |
| 400 | InvalidOnDemandUrl.Unsafe | Specified OnDemandUrl is not safe. | - |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|