Sends a message to a user.
Operation description
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.
Debugging
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 Resourcesis 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:SendLiveMessageUser | create | *Rtc acs:live::{#accountId}:rtc/{#AppId} |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| AppId | string | Yes | The ID of the interactive messaging application in which the message is sent. | demo |
| ReceiverId | string | Yes | The ID of the user who receives the message. The ID can be up to 64 bytes in length and can contain letters and digits. | uid2 |
| SenderId | string | Yes | The ID of the user who sends the message. The ID can be up to 64 bytes in length and can contain letters and digits. | uid1 |
| SenderInfo | string | No | The additional information about the user who sends the message. It can be up to 512 bytes in length. | uid1meta1 |
| Body | string | No | The message body. It can be up to 15 KB in length. | hello, user |
| MsgType | long | No | The message type. | 2 |
| MsgTid | string | No | The ID of the message, which is a unique identifier that can be used to delete the message. The ID can be up to 64 bytes in length and can contain letters and digits. | 169830**** |
| 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
Examples
Sample success responses
JSONformat
{
"RequestId": "6CFDE7AB-571A-14EA-B072-989FF753****"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | InputInvalid | %s. | Illegal input parameters |
| 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 |
|---|