Queries the configurations of primary/secondary stream mixing.

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. For more information, see QPS limit on an API operation in ApsaraVideo Live.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request parameters

Parameter Type Required Example Description
Action String Yes DescribeLiveStreamMerge

The operation that you want to perform. Set the value to DescribeLiveStreamMerge.

DomainName String Yes example.com

The streaming domain.

AppName String No app

The name of the application that generates the output stream.

StreamName String No StreamName

The name of the output stream.

Protocol String No rtmp

The streaming protocol. Valid values:

  • rtmp: This is the default value.
  • rtc

Response parameters

Parameter Type Example Description
RequestId String 16A96B9A-F203-4EC5-8E43-CB92E68F4CD8

The ID of the request.

LiveStreamMergeList Array of LiveStreamMerge
LiveStreamMerge
Protocol String rtmp

The streaming protocol.

StreamName String StreamName

The name of the output stream.

InAppName2 String app2

The name of the application that generates the input secondary stream.

ExtraInAppStreams String app3/stream3,app4/stream4,app5/stream5,…,appN/streamN

The names of the applications that generate the input additional streams other than the primary stream and secondary stream, and the names of these additional streams.

InStreamName1 String InStream1

The name of the input primary stream.

StreamUsing String InStream1

The stream that is being used.

DomainName String example.com

The streaming domain.

AppUsing String app1

The application that is being used.

InStreamName2 String stream2

The name of the input secondary stream.

EndTime String 2020-05-29T01:00:00Z

The end time of the stream mixing.

AppName String app

The name of the application that generates the output stream.

StartTime String 2020-05-29T00:00:00Z

The start time of the stream mixing.

InAppName1 String app1

The name of the application that generates the input primary stream.

Examples

Sample requests

http(s)://live.aliyuncs.com/?Action=DescribeLiveStreamMerge
&DomainName=example.com
&AppName=app
&StreamName=StreamName
&Protocol=rtmp
&<Common request parameters>

Sample success responses

XML format

HTTP/1.1 200 OK
Content-Type:application/xml

<DescribeLiveStreamMergeResponse>
    <RequestId>16A96B9A-F203-4EC5-8E43-CB92E68F4CD8</RequestId>
    <LiveStreamMergeList>
        <Protocol>rtmp</Protocol>
        <StreamName>StreamName</StreamName>
        <InAppName2>app2</InAppName2>
        <ExtraInAppStreams>app3/stream3,app4/stream4,app5/stream5,…,appN/streamN</ExtraInAppStreams>
        <InStreamName1>InStream1</InStreamName1>
        <StreamUsing>InStream1</StreamUsing>
        <DomainName>example.com</DomainName>
        <AppUsing>app1</AppUsing>
        <InStreamName2>stream2</InStreamName2>
        <EndTime>2020-05-29T01:00:00Z</EndTime>
        <AppName>app</AppName>
        <StartTime>2020-05-29T00:00:00Z</StartTime>
        <InAppName1>app1</InAppName1>
    </LiveStreamMergeList>
</DescribeLiveStreamMergeResponse>

JSON format

HTTP/1.1 200 OK
Content-Type:application/json

{
  "RequestId" : "16A96B9A-F203-4EC5-8E43-CB92E68F4CD8",
  "LiveStreamMergeList" : [ {
    "Protocol" : "rtmp",
    "StreamName" : "StreamName",
    "InAppName2" : "app2",
    "ExtraInAppStreams" : "app3/stream3,app4/stream4,app5/stream5,…,appN/streamN",
    "InStreamName1" : "InStream1",
    "StreamUsing" : "InStream1",
    "DomainName" : "example.com",
    "AppUsing" : "app1",
    "InStreamName2" : "stream2",
    "EndTime" : "2020-05-29T01:00:00Z",
    "AppName" : "app",
    "StartTime" : "2020-05-29T00:00:00Z",
    "InAppName1" : "app1"
  } ]
}

Error codes

HttpCode Error code Error message Description
400 ConfigAlreadyExists Config has already exist. The error message returned because the configuration already exists.

For a list of error codes, see Service error codes.