List tickets
List or file tickets. The list comes in Board order: open tickets high, normal, low, in work order (rank) within each, then done and rejected ones, the latest changed first. It also has kinds (the kinds a ticket can have, see Kind), labels (the labels tickets have, A to Z, see Labels), wipLimit, leadStarts (the number you let the Lead start tickets up to, or 0) and leadStartsLeft. A ticket has approvedBy (you or Lead) once it is put in Ready. The room page gets the same list as a tickets event on its GET /stream when it opens the stream with board=1, with people, who sits on each ticket, and without the time each pipeline was checked. The stream’s hello says whether it will (tickets). It is sent once as the stream opens, then only when it changes, and only to the room page on this computer.
Tokens: the relay key, and the token of any session, the COO, the security officer. A route a token reaches can still refuse it, as the description says.
From docs/manual/relay.html#routes.