Mobile

Clears the unread dot for the calling agent, and for them alone — a colleague opening the ticket does not clear mine.

Explicit rather than implied by GET /tickets/{number}: a read that happens as a side effect of fetching cannot be retried, prefetched or cached, and a client fetches a ticket for reasons other than a human reading it.

Exchanges an agent's credentials for a token bound to this phone, revocable on its own. Call it on the workspace's own address ({slug}.$BASE_DOMAIN): the workspace comes from the host, never from the body.

Unauthenticated, so it is limited separately — ten attempts per address and forty per source every five minutes.

The browser leg of a single sign-on. Open the workspace's login page in a system browser with ?next=/api/v1/auth/authorize?code_challenge=…; once the identity provider has signed the agent in, this route redirects to the app's URL scheme carrying a one-time code, which the app spends on /auth/exchange.

The destination is the scheme configured on the instance — there is no redirect_uri parameter, by design. PKCE S256 is required: a custom scheme is not exclusive to one installed app.

Trades the one-time code for a device session. Single use, two minutes, and worthless without the verifier the app kept.

Revokes the session the call is made with, and its push registrations. Other devices and browser sessions are untouched.

Identity, role and teams — what "my tickets" and the view switcher are built from. Needs an agent session: a workspace API key has nobody behind it and gets 403 agent_required.

available is the only writable field, and it is not cosmetic: round-robin assignment only ever picks an available agent, so turning it off on the way into a meeting is how a queue stops filling up for somebody who cannot answer.

A name, an email or a role are the workspace's business. An endpoint called /me that could change a role would be a privilege escalation with a friendly name.

Upsert on the token: the operating system rotates and reissues it, so re-registering updates the row instead of leaving a trail of them.

An agent revokes their own registrations; a device is not workspace furniture.

The same feed the web topbar shows, as data rather than as sentences — a phone writes its own wording, in the language of the phone.

read is not per item and cannot be: the feed is derived from tickets and messages, so there is no row to mark. It is a waterline (see POST /notifications/read).

Moves the waterline to now. Shared with the web topbar's own button, so clearing the badge on a phone clears it in the browser too.

One query across four collections, as the search box offers it. A few top matches per kind, no pagination — page /tickets with real filters to walk a set.