All Products
Search
Document Center

ApsaraVideo Live:UpdateLiveCenterTransfer

Last Updated:Nov 14, 2024

Modifies the configurations of live center stream relay.

Operation description

You can call this operation to modify only the time-related parameters, including TransferArgs, StartTime, and EndTime.

QPS limit

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

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:UpdateLiveCenterTransferupdate
*Domain
acs:cdn:*:{#accountId}:domain/{#DomainName}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
DomainNamestringYes

The streaming domain.

example.com
AppNamestringYes

The name of the application to which the live stream belongs. The value of this parameter must be the same as the application name for the live stream that you want to relay. Otherwise, the configuration does not take effect. You can view the application name on the Stream Management page of the ApsaraVideo Live console.

testapp
StreamNamestringYes

The name of the live stream. You can view the stream name on the Stream Management page of the ApsaraVideo Live console.

teststream
DstUrlstringYes

The third-party URL to which the live stream is relayed. You can add only one URL.

Note The protocol that the URL uses must be the same as the protocol of the live stream. Only URLs over RTMP and SRT are supported.
rtmp://push.example2.aliyunlive.com/testapp1/teststream2
TransferArgsstringYes

The validity period of stream relay. Valid values:

  • always: The stream can always be relayed.
  • time: The stream can be relayed in a specified time period.
Note If the value is time, StartTime and EndTime are required.
always
StartTimestringNo

The start time of stream relay. Specify the time in the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time must be in UTC.

2017-12-21T10:00:00Z
EndTimestringNo

The end time of stream relay. Specify the time in the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time must be in UTC.

Note The end time must be later than the start time.
2017-12-22T08:00:00Z

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The ID of the request.

7908F2FF-44F8-120F-9FD6-85AE4B6C19EC

Examples

Sample success responses

JSONformat

{
  "RequestId": "7908F2FF-44F8-120F-9FD6-85AE4B6C19EC"
}

Error codes

HTTP status codeError codeError messageDescription
400InvalidParamParameter invalid.Illegal input parameters
400CodeIllegalDurationparam end_time is before start_time-
500InternalErrorThe request processing has failed due to backend service exception.-

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

Change history

Change timeSummary of changesOperation
2023-03-14The Error code has changedView Change Details