DeleteEventSub - Delete event subscription callback - ApsaraVideo Live

Operation description

Before you call this operation, you must have called CreateEventSubscribe to create an event subscription callback.

QPS limit

You can call this operation up to 100 times per second per account. Requests that exceed this limit are dropped, which may interrupt your service.

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

get

*Rtc

acs:live:*:{#accountId}:rtc/{#AppId}

None

Request parameters

Parameter	Type	Required	Description	Example
AppId	string	Yes	The ID of the application.	9qb1****
SubscribeId	string	Yes	The subscription ID. Obtain this from the CreateEventSub response.	ad53276431c****

Response elements

Element	Type	Description	Example
	object	The response body.
RequestId	string	The request ID.	760bad53276431c499e30dc36f6b26be

Examples

Success response

JSON format

{
  "RequestId": "760bad53276431c499e30dc36f6b26be"
}

Error codes

HTTP status code	Error code	Error message	Description
400	InputInvalid	%s.	Illegal input parameters
500	ServerError	%s.	Internal error. Try again later or submit a ticket.
403	NoAuth	%s.	No permission
404	ResourceNotExist	%s.	The specified resource does not exist.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.