All Products
Search
Document Center

:AddLiveCenterTransfer

Dernière mise à jour :Jul 31, 2026

Adds a live center stream relay configuration.

Operation description

The single-user QPS limit of this API is 100 calls per second. If the limit is exceeded, API calls will be throttled, which may affect your business. Please make calls appropriately.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

  • Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.

  • API: The API that you can call to perform the action.

  • Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.

  • Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.

    • For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.

    • For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.

  • Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.

  • Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

live:AddLiveCenterTransfer

create

*Domain

acs:cdn:*:{#accountId}:domain/{#DomainName}

None None

Request parameters

Parameter

Type

Required

Description

Example

DomainName

string

Yes

The region ID.

example.com

AppName

string

Yes

The streaming domain.

testapp

StreamName

string

Yes

The name of the live stream application. The AppName you enter must be the same as the AppName of the live stream to be relayed for the configuration to take effect. You can view the AppName on the Stream Management page.

teststream

DstUrl

string

Yes

The name of the live stream. You can view the StreamName on the Stream Management page.

rtmp://push.example2.aliyunlive.com/testapp1/teststream2

TransferArgs

string

Yes

The third-party live streaming address for relay. You can add up to one address.

Note

The protocol of the destination address must be the same as the protocol of the live stream to be relayed. Only RTMP and SRT relay addresses are supported.

always

StartTime

string

No

The validity period of the relay. Valid values:

  • always: permanently effective.

  • time: effective within the specified time period.

Note

If the value is time, StartTime and EndTime are required.

Valid values:

  • always :

    Permanently effective

  • time :

    Effective within the specified time period

2017-12-21T10:00:00Z

EndTime

string

No

The start time of the relay. The date format follows the ISO 8601 notation and uses UTC+0 time. The format is yyyy-MM-ddTHH:mm:ssZ.

2017-12-22T08:00:00Z

EndTime

string

No

The end time of the relay. The date format follows the ISO 8601 notation and uses UTC+0 time. The format is yyyy-MM-ddTHH:mm:ssZ.

Note

The end time must be later than the start time.

2017-12-22T08:00:00Z

Response elements

Element

Type

Description

Example

object

RequestId

string

The request ID.

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

Examples

Success response

JSON format

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

Error codes

HTTP status code

Error code

Error message

Description

400 InvalidParam Parameter invalid. Illegal input parameters
400 CenterTransfersStreamOverLimit CenterTransfers stream is over limit for this domainName.
400 ConfigAlreadyExists Config has already exist.
400 CodeIllegalDuration param end_time is before start_time
500 InternalError The request processing has failed due to backend service exception.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.