All Products
Search

This Product

    :DeleteLiveEdgeTransfer

    Document Center

    :DeleteLiveEdgeTransfer

    Dernière mise à jour :Jul 31, 2026

    Deletes a live edge transfer configuration.

    Operation description

    The DeleteLiveEdgeTransfer operation deletes only the live edge transfer configuration for a specific domain name. It does not affect any ongoing live stream transfers based on this configuration. The following table describes typical scenarios.

    ScenarioAnalysisResult
    1. After a live edge transfer configuration is set up by calling SetLiveEdgeTransfer, an ingest is started. The configuration is then deleted by calling DeleteLiveEdgeTransfer while the ingest is in progress.The live edge transfer configuration exists when the ingest starts.The ingest is not affected, and the live stream transfer is not interrupted.
    2. The live edge transfer configuration is deleted by calling DeleteLiveEdgeTransfer during an ingest. The ingest is then stopped and restarted.The live edge transfer configuration no longer exists when the ingest is restarted.A live edge transfer is not initiated.
    3. An ingest is started after the live edge transfer configuration is deleted by calling DeleteLiveEdgeTransfer.The live edge transfer configuration does not exist at this time.A live edge transfer is not initiated.

    QPS limit

    The queries per second (QPS) limit for this operation is 100 per user. Throttling is triggered if the limit is exceeded. We recommend that you abide by this limit to prevent impacts on your business. For more information, see QPS limits.

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

    delete

    *All Resource

    *

    		 None None

    Request parameters

    Parameter

    Type

    Required

    Description

    Example
    RegionId

    string

    No

    The ID of the region.

    cn-shanghai
    DomainName

    string

    Yes

    The ingest domain name. You can configure only one live edge transfer configuration for each domain name.

    demo.aliyundoc.com

    Response elements

    Element

    Type

    Description

    Example

    object

    RequestId

    string

    The ID of the request.

    16A96B9A-F203-4EC5-8E43-CB92E68F4CD8

    Examples

    Success response

    JSON format

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

    Error codes

    HTTP status code

    Error code

    Error message

    Description
    400 InvalidParam Parameter invalid. Illegal input parameters
    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.