session-name. Every participant's copy is renamed, and every participant gets a chat-name-change message.messagesession-participants with the complete list of user IDs, including your own, for example 1001@example.com,1002@example.com,1003@example.com. A user added gets the session, and a user left out loses it. The other participants get a chat-participant-add or chat-participant-remove message, and a removed user gets a chat-participant-remove-notification. Use it on a group chat only.403. Marking read or muted touches only the path user's copy and needs no such check. To leave a group yourself, use PUT /domains/{domain}/users/{user}/messagesessions/{messagesession}/leave.messagesession-last-status read after the user has seen the last message, or messagesession-muted yes or no. Only your own copy changes.202 means the change is accepted and applied shortly after, so a read made right away can still show the old values. When you only mark read or muted, a session ID the user does not have changes nothing and still answers 202.Authorization: Bearer ********************curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/domains//users//messagesessions/b1946ac92492d2347c6235b4d2611184' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"session-name": "Front Desk"
}'{
"code": 202,
"message": "Accepted"
}