Accept call queue conversation

PUT

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

Last modified:2026-10-07 23:43:50

OperationId:AcceptMessageSession

Takes an SMS conversation that is waiting in a call queue and assigns it to the user, as its agent. 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. POST does the same as PUT.

Send the queue's user ID in messagesession-queue-termination, as the session shows it. The session moves to active for this user, and messagesession-agent-start-datetime is set.

Below Office Manager, the user in the path must be an agent of the queue the conversation is waiting in, as the user itself or through one of its devices, or the user the conversation was already offered to. Anyone else gets 403. Office Manager and above can assign the conversation to any user.

When another agent already has the conversation, or every copy is complete, the answer is 200 with a body whose code is 400 and status is failure, and nothing changes. Check code in the body, not only the HTTP status.

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

Body Params application/jsonRequired

Examples

Responses

🟢202Accepted

application/json

The change is accepted and applied shortly after this response.

Bodyapplication/json

🟢200Not accepted

🟠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/example.com/users/1001/messagesessions/aab3238922bcc25a6f606eb525ffdc56/accept' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "messagesession-queue-termination": "2000@example.com"
}'

Response Example

202 - Accept

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

Modified at 2026-10-07 23:43:50

Create message session

Count message sessions