StopRtcCloudTranscode

Updated at:

Stops a cloud transcoding task.

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

none

*All Resource

*

None None

Request syntax

POST  HTTP/1.1

Request parameters

Parameter

Type

Required

Description

Example

AppId

string

Yes

The application ID. It can contain uppercase and lowercase letters, digits, underscores (_), and hyphens (-), and can be up to 64 characters in length.

********-7074-****-9ef5-85c19a4*****

TaskId

string

Yes

The cloud transcoding task ID. It can contain uppercase and lowercase letters, digits, underscores (_), and hyphens (-), and can be up to 64 characters in length.

******73-8501-****-8ac1-72295a******

Response elements

Element

Type

Description

Example

object

The response content.

RequestId

string

The request ID.

******3B-0E1A-586A-AC29-742247******

Examples

Success response

JSON format

{
  "RequestId": "******3B-0E1A-586A-AC29-742247******"
}

Error codes

HTTP status code

Error code

Error message

Description

400 InvalidParameter%s %s.
400 MissingParameter%s %s.
400 TooManyRequests %s.
500 InternalError %s. error on the live liveapi server.
403 Forbidden %s.
404 NotFound%s %s.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.