All Products
Search

This Product

    ApsaraVideo Live:AddLivePackageConfig

    Document Center

    ApsaraVideo Live:AddLivePackageConfig

    Last Updated:Jan 20, 2026

    You can call the AddLivePackageConfig operation to add a live stream packaging configuration.

    Operation description

    • When you add a packaging configuration to a domain name for the first time, the related acceleration configurations for the playback domain name are also applied. The configurations take effect in 3 to 5 minutes.

    • If the playback domain name is in a region outside China, such as Singapore, Germany, Japan, or Indonesia, high latency may occur. After you add the configuration, test it to ensure it works as expected.

    • After you add a live stream packaging configuration, you must restart the stream ingest for the configuration to take effect.

    QPS limit

    The queries per second (QPS) limit for a single user is 300 calls per minute. If you exceed the limit, API calls are throttled. This may affect your business. Plan your calls accordingly.

    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:AddLivePackageConfig

    create

    *Domain

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

    		 None None

    Request parameters

    Parameter

    Type

    Required

    Description

    Example
    RegionId

    string

    No

    The region ID.

    cn-shanghai
    DomainName

    string

    Yes

    The live streaming domain name. This is the primary playback domain name.

    example.com
    AppName

    string

    Yes

    The AppName must match the AppName in the ingest URL for the template to take effect. The AppName can be up to 255 characters in length and can contain digits, uppercase letters, lowercase letters, hyphens (-), and underscores (_). A hyphen or an underscore cannot be the first character. You can also set this parameter to a single asterisk (*) to match all AppNames.

    AppName
    StreamName

    string

    Yes

    The StreamName must match the StreamName in the ingest URL for the template to take effect. The StreamName can be up to 255 characters in length and can contain digits, uppercase letters, lowercase letters, hyphens (-), and underscores (_). A hyphen or an underscore cannot be the first character. You can also set this parameter to a single asterisk (*) to match all StreamNames.

    StreamName
    Protocol

    string

    Yes

    The live streaming protocol and container format. Valid values:

    • HLS_CMAF

    • LLHLS_TS (low latency)

    • LLHLS_CMAF (low latency)

    • DASH_CMAF

    • HLSDASH_CMAF

    HLS_CMAF
    SegmentNum

    integer

    No

    The number of M3U8 segments for live streaming.

    • Valid values: 3 to 10.

    • Default value: 3.

    3
    SegmentDuration

    integer

    No

    The segment length, in seconds.

    • If you set Protocol to HLS_CMAF, the valid values are 1 to 10. The default value is 5.

    • If you set Protocol to LLHLS_*, the valid values are 1 to 2. The default value is 1.

    5
    PartDuration

    integer

    No

    The length of the part segment, in milliseconds.

    • If SegmentDuration is 1 s, the valid values are 100 to 500. The default value is 350.

    • If SegmentDuration is 2 s, the valid values are 100 to 1000. The default value is 700.

    • This parameter is valid only when you set Protocol to LLHLS_*.

    350
    IgnoreTranscode

    boolean

    No

    Specifies whether to ignore transcoded streams. Valid values:

    • true (default): Ignore transcoded streams.

    • false: Do not ignore transcoded streams.

    true

    Response elements

    Element

    Type

    Description

    Example

    object

    RequestId

    string

    The request ID.

    05D00B48-DF50-5DC0-A07D-A250DFAE****

    Examples

    Success response

    JSON format

    {
  "RequestId": "05D00B48-DF50-5DC0-A07D-A250DFAE****"
}

    Error codes

    HTTP status code

    Error code

    Error message

    Description
    400 MissingParam %s, please check and try again later. Parameter is missing, please check and try again.
    400 InvalidParams %s, please check and try again later. Parameter is invalid, please check and try again.
    400 ConfigAlreadyExists %s Please check and try again later. Configuration already exists, please check and try again.
    400 InvalidProtocol %s, please check and try again later. The parameter Protocol is invalid, please check and try again.
    400 InvalidSegmentNum %s, please check and try again later. The parameter SegmentNum is invalid, please check and try again.
    400 InvalidSegmentDuration %s, please check and try again later. The parameter SegmentDuration is invalid, please check and try again.
    400 InvalidPartDuration %s, please check and try again later. The parameter PartDuration is invalid, please check and try again.
    500 InternalErr %s, please try again. Internal error, please try again later.
    500 DomainConfigFailed %s, please try again later. Domain name configuration failed, please try again later.
    409 ConfigConflicts %s, please check and try again later. Configuration conflict, please check and try again.

    See Error Codes for a complete list.

    Release notes

    See Release Notes for a complete list.