ModifyLiveMessageAppCallback - ApsaraVideo Live - Alibaba Cloud Documentation Center

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
live:ModifyLiveMessageAppCallback	update	*Rtc `acs:live::{#accountId}:rtc/{#AppId}`	none	none

Request parameters

Parameter	Type	Required	Description	Example
AppId	string	Yes	The ID of the interactive messaging application whose callback settings you want to modify.	demo
EventCallbackUrl	string	No	The callback URL for events such as user logon, logoff, joining a group, and leaving a group. If you leave this parameter empty, callbacks are disabled. The callback URL must start with http:// or https:// and cannot contain a private IP address or a port number.	http://example.aliyundoc.com/examplecallback
DataCenter	string	No	The data center. It must be the same as the data center that was specified when you called the CreateLiveMessageApp operation to create the interactive messaging application. Valid values: cn-shanghai and ap-southeast-1 (Singapore).	cn-shanghai

Response parameters

Parameter	Type	Description	Example
	object
RequestId	string	The request ID.	1F0FFEAD-B7D5-1D4A-A6B9-8C63ADF6****
AppId	string	The ID of the interactive messaging application.	demo
AppSign	string	The signature of the interactive messaging application. It is required by the interactive messaging SDK.	**************************************************************************
EventCallbackUrl	string	The callback URL for events such as user logon, logoff, joining a group, and leaving a group. This parameter is not returned if it has an empty value.	http://example.aliyundoc.com/examplecallback
EventCallbackNeedAuthentication	boolean	Indicates whether authentication is required for event callbacks. Default value: true.	true

Examples

Sample success responses

JSONformat

{
  "RequestId": "1F0FFEAD-B7D5-1D4A-A6B9-8C63ADF6****",
  "AppId": "demo",
  "AppSign": "**************************************************************************",
  "EventCallbackUrl": "http://example.aliyundoc.com/examplecallback",
  "EventCallbackNeedAuthentication": true
}

Error codes

HTTP status code	Error code	Error message	Description
400	InputInvalid	%s.	Illegal input parameters
400	ErrorInvalidEventCallbackUrl	%s.	The EventCallbackUrl is invalid, please check and try again.
403	NoAuth	%s.	No permission
404	ResourceNotExist	%s.	The requested resource does not exist, please check and try again
500	ServerError	%s.	Unknown error, please try again later or submit a ticket for consultation.

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation
2024-02-02	The Error code has changed	View Change Details