Known contacts
People outside the team the workspace is already in touch with outside Roster: email addresses, domains (everyone there, subdomains included) and phone numbers. A hire's first email, text or help-desk reply to one of them doesn't wait for approval. source is added (by someone here) or approval (added when someone approved a first message to them). Newest first.
sessionbetter-auth.session_token<token>Set by POST /api/auth/sign-in/email.
ws*stringThe workspace id (from GET /api/me).
The workspace's known contacts.
application/jsoncurl -X GET 'https://app.useroster.work/api/workspaces/string/known-contacts'{ "contacts": [ { "id": "3f1c…", "value": "client.example", "kind": "domain", "source": "added", "createdAt": "2026-11-06T09:00:00.000Z" }, { "id": "9a2e…", "value": "+971501234567", "kind": "phone", "source": "approval", "createdAt": "2026-11-05T15:12:00.000Z" } ]}Change workspace settings PATCH
Change only what's given. Owners and admins only. Hires never claim to be a person, whatever this says; `discloseAi` is about saying so up front.
Add known contacts POST
Owners and admins only. Each value is an email address, a domain (`client.example` or `@client.example`) or a phone number with country code; addresses and domains are kept in lower case, numbers as `+` and digits. Values already kept are left as they are, and only the new ones come back.