All Products
Search
Document Center

ApsaraVideo Live:CreateLiveDelayConfig

Last Updated:Nov 14, 2024

Adds a stream delay configuration.

Operation description

Stream delay is different from latency caused by streaming protocols. Stream delay is a feature that allows you to delay the playback of a live stream that is processed in the cloud.

You can call this operation up to 60 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

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

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 Resources is 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.
OperationAccess levelResource typeCondition keyAssociated operation
live:CreateLiveDelayConfigget
*Domain
acs:cdn:*:{#accountId}:domain/{#DomainName}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
DomainstringYes

The main streaming domain.

example.com
AppstringYes

The name of the application to which the live stream belongs. You can specify an asterisk (*) as the value to match all applications that belong to the domain name.

liveApp****
StreamstringYes

The name of the live stream. You can use the wildcard (*) to specify all streams of the application.

liveStream****
DelayTimeintegerYes

The duration for which the playback of the live stream is delayed. The value must be an integer. Valid values: 16 to 3600. Unit: seconds.

60
TaskTriggerModestringYes

The trigger mode. Valid values:

  • PUBLISH_ONLY: Stream delay can be triggered only by specifying the stream delay parameter in the ingest URL.
  • CONFIG_ONLY: Stream delay can be triggered only by the stream delay configuration.
  • PUBLISH_CONFIG: Stream delay can be triggered by the stream delay parameter in the ingest URL or the stream delay configuration. The stream delay parameter takes precedence over the stream delay configuration.
PUBLISH_ONLY

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The request ID.

16A96B9A-F203-4EC5-8E43-CB92E68F4CD8

Examples

Sample success responses

JSONformat

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

Error codes

HTTP status codeError codeError message
400InvalidParameters%s

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
No change history