Profile
The authenticated user's own profile, preferences, presence and avatar.
Update the authenticated user's profile and preferences
Partial update of the acting user's own name, preferences (locale,
Set the authenticated user's real-time availability
Sets the acting agent's presence (online / away / busy / offline),
I am still here
The panel and the app call it while open. Routing that asks for a fresh
Book my leave
While the leave covers now the caller is not given new work and their
End or cancel my leave
End or cancel my leave
My unsent drafts
Every live draft of the caller (idle under 30 days), across all their
One of my drafts
One of my drafts
Save one of my drafts
Last write wins by `revision` (the client's edit time, epoch ms): when
Throw one of my drafts away
Idempotent. Other open devices hear `draft.deleted`. Accepted sends spend their draft server-side by themselves.
My own notification mutes
The caller's own mutes in force (doc 64 §9A-S3). Requires
Mute a channel, a contact or a conversation for myself
Stop push / e-mail / SMS interruptions about the subject for the caller
Remove one of my mutes
Remove one of my mutes
Set whether a live customer call may ring the authenticated agent
Sets the acting agent's CALL availability (SES-1 F2). Deliberately not
Upload or replace the authenticated user's avatar
Multipart upload of a single avatar image, stored on the tenant-scoped
Whether the member can say the two-factor code again, and until when it holds
Doc 106 §26-1, CMP-5 — before custom tag code goes live. `methods` are the factors usable here (authenticator app, e-mail code, recovery code; SMS is not offered).
Say the two-factor code again (holds 15 minutes)
Doc 106 §26-1, CMP-5. 422 for a wrong code. Audit rows `security.step_up` / `security.step_up_failed`.
E-mail the member a two-factor code for a step-up
Doc 106 §26-1, CMP-5 — only for an account with e-mail codes on (422 otherwise).
Get the account's phone + verification state
The signed-in account's phone number and whether it is SMS-verified.
Set the account's phone and text a verification code
Sets (replaces) the account's phone — marked unverified — and texts an SMS code via the platform gateway.
Confirm the account's phone with the SMS code
Confirm the account's phone with the SMS code
Re-text the account phone-verification code
Always 200 (a no-op when the account has no phone or is already verified).
Read the member's own personal email mailbox
The member's private email channel (IMAP piping + SMTP). `exists:false` when not set up. Viewing is always allowed.
Create or update the member's own personal email mailbox
Requires the `agent_email_piping.manage` permission (admins always). Partial — only the keys sent are touched. Sending `piping.history_sync` additionally requires that the caller manages this mailbox's history sync (see `MailHistorySync.can_manage`); otherwise 403 and nothing changes.
Remove the member's own personal email mailbox
Requires the `agent_email_piping.manage` permission. Existing conversations remain.