All Products
Search

This Product

    :AddLiveStreamMerge

    Document Center

    :AddLiveStreamMerge

    Last Updated:Nov 14, 2024

    Invoke AddLiveStreamMerge to add primary and backup stream merging configuration.

    Operation description

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

    Request parameters

    ParameterTypeRequiredDescriptionExample
    DomainNamestringYes

    The streaming domain.

    		example.com
    AppNamestringYes

    The name of the application that generates the output stream. The value must be the same as the application name in the ingest URL of the output stream. Otherwise, the configuration does not take effect. You cannot set the value to an asterisk (*).

    		app
    StreamNamestringYes

    The name of the output stream. The value must be the same as the stream name in the ingest URL of the output stream. Otherwise, the configuration does not take effect. You cannot set the value to an asterisk (*).

    		StreamName
    InAppName1stringYes

    The name of the application that generates the input primary stream. The value must be the same as the application name that is specified in the ingest URL of the primary stream. Otherwise, the configuration does not take effect.

    		app1
    InStreamName1stringYes

    The name of the input primary stream. The value must be the same as the stream name that is specified in the ingest URL of the primary stream. Otherwise, the configuration does not take effect.

    		InStream1
    InAppName2stringYes

    The name of the application that generates the input secondary stream. The value must be the same as the application name that is specified in the ingest URL of the secondary stream. Otherwise, the configuration does not take effect.

    		app2
    InStreamName2stringYes

    The name of the input secondary stream. The value must be the same as the stream name that is specified in the ingest URL of the secondary stream. Otherwise, the configuration does not take effect.

    		stream2
    StartTimestringYes

    The start time of the stream mixing.

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

    		2020-05-29T00:00:00Z
    EndTimestringYes

    The end time of the stream mixing.

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

    Note The interval between the start time and the end time must be within 7 days.
    		2020-05-29T01:00:00Z
    ProtocolstringNo

    The streaming protocol. Valid values:

    • rtmp: This is the default value.
    • rtc
    		rtmp
    Note Any two of the AppName, InAppName1, and InAppName2 parameters cannot have the same values. Any two of the StreamName, InStreamName1, and InStreamName2 parameters cannot have the same values.

    Response parameters

    ParameterTypeDescriptionExample
    object
    RequestIdstring

    The request ID.

    		16A96B9A-F203-4EC5-8E43-CB92E68F****

    Examples

    Sample success responses

    JSONformat

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

    Error codes

    HTTP status codeError codeError messageDescription
    400InvalidStartTime.MalformedSpecified parameter StartTime is not valid.-
    400InvalidEndTime.MalformedSpecified parameter EndTime is not valid.-
    400InvalidStartTime.ValueNotSupportedThe specified value of parameter StartTime is not supported.The value specified for the StartTime parameter is invalid.
    400InvalidParamParameter invalid.Illegal input parameters
    400QuotaExceeded.MergeExceed max merge count limit-
    400ConfigAlreadyExistsConfig has already exist.-
    400Duration.ExceedDuration between StartTime and EndTime is too long.-
    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
    No change history