A ticket for the socket

GET

/chat/ticket

A browser cannot put a bearer header on a WebSocket and a token in a
URL ends up in logs, so the socket is opened with a two-minute token
of its own, presented once as ?ticket= to GET /chat/ws?conversation=<id>
(a WebSocket upgrade, handled outside these routes). The socket speaks
{ event, data } both ways: message, typing, presence, read
from the server; typing, ping from the client. Messages themselves
are sent through POST …/messages.

Request

None

Responses

🟢200

application/json

The ticket

Bodyapplication/json

Response Example

{
    "ticket": "string",
    "expiresIn": 0,
    "live": true
}

Modified at 2026-10-05 04:04:32

Every support conversation, open first

One conversation, with who is in it and who is connected