All Products
Search
Document Center

ApsaraVideo Live:DeleteLiveMessageUserMessage

Last Updated:Nov 14, 2024

Deletes a message that is sent to a user.

Operation description

QPS limit

You can call this operation up to 50 times per second per account. Requests that exceed this limit are dropped and you will experience service interruptions. We recommend that you take note of this limit when you call this operation. For more information, see QPS limits.

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.

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.
OperationAccess levelResource typeCondition keyAssociated operation
live:DeleteLiveMessageUserMessagedelete
*Domain
acs:live:*:{#accountId}:domain/{#DomainName}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
AppIdstringYes

The application ID.

demo
ReceiverIdstringYes

The ID of the user who received the message to delete. The ID can contain only letters and digits and can be up to 64 bytes in length.

169830****
MessageIdstringYes

The ID of the message that you want to delete. Set this parameter to the value of MsgTid that you specified when you called the SendLiveMessageUser operation. The ID can contain only letters and digits and can be up to 64 bytes in length.

**********
DeleterIdstringNo

The ID of the user who performs the deletion operation. The ID can contain only letters and digits and can be up to 64 bytes in length.

169830****
DeleterInfostringNo

The additional information about the user who performs the deletion operation. The value can be up to 512 bytes in length.

username
DataCenterstringNo

The data center where the interactive messaging application is deployed. Set this parameter to the value of DataCenter that you specified when you called the CreateLiveMessageApp operation. Valid values: cn-shanghai (Shanghai) and ap-southeast-1 (Singapore).

cn-shanghai

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The request ID.

6CFDE7AB-571A-14EA-B072-989FF753****

Examples

Sample success responses

JSONformat

{
  "RequestId": "6CFDE7AB-571A-14EA-B072-989FF753****"
}

Error codes

HTTP status codeError codeError messageDescription
400InputInvalid%s.Illegal input parameters
403NoAuth%s.No permission
404ResourceNotExist%s.The requested resource does not exist, please check and try again
500ServerError%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 timeSummary of changesOperation
No change history