Modifies the information about a user.
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 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:ModifyLiveMessageUserInfo | update | *All Resources * |
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
AppId | string | Yes | The ID of the interactive messaging application whose user information you want to modify. | demo |
UserId | string | Yes | The ID of the user whose information you want to modify. | uid2 |
UserMetaInfo | string | No | The additional information about the user after the modification. The value can be up to 512 bytes in length. | uid2meta2 |
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
JSON
format
{
"FailList": [
{
"Code": 440,
"GroupId": "grouptest2",
"Reason": "group not exists or already deleted",
"Success": false
}
],
"RequestId": "3271ACD2-F143-1204-AFDB-9A87C131****",
"SuccessList": [
{
"GroupId": "grouptest1",
"Success": true
}
]
}
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 |
---|---|---|
2024-05-10 | The Error code has changed. The response structure of the API has changed | View Change Details |