Leave message session

PUT

/domains/{domain}/users/{user}/messagesessions/{messagesession}/leave

Last modified:2026-10-09 00:40:44

OperationId:leaveMessagesession

Takes the user out of a group chat. Every scope reaches its own user. Office Manager reaches every user in its domain, Reseller the domains in its territory, and Super User every domain.

The user's copy of the session is hidden, the other participants' lists drop the user, and they get a chat-participant-leave message naming the user. The session must be a group chat: a one-to-one session answers 400. To hide a one-to-one session, use DELETE /domains/{domain}/users/{user}/messagesessions/{messagesession}. POST does the same as PUT.

Below Office Manager, your token's user must be a participant of the session, or the answer is 403, and the remaining participants are always worked out from the session.

A 202 means the change is accepted and applied shortly after, so a read made right away can still show the old values.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Path Params

Responses

🟢202Accepted

application/json

The change is accepted and applied shortly after this response.

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Not Found

🟠420Rate Limit Exceeded

Request Example

Shell

JavaScript

Java

Swift

curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/domains//users//messagesessions/b1946ac92492d2347c6235b4d2611184/leave' \
--header 'Authorization: Bearer <token>'

Response Example

202 - Left

{
    "code": 202,
    "message": "Accepted"
}

Modified at 2026-10-09 00:40:44

List messages in session

Delete message session