Forget a known contact
Owners and admins only. A hire's first message to them waits for approval again, unless the connection has been in touch with them already.
sessionbetter-auth.session_token<token>Set by POST /api/auth/sign-in/email.
ws*stringThe workspace id (from GET /api/me).
id*stringThe id of what the path names: a hire, a connection, a skill, a shared file, a department, a position, a goal or an approval.
Forgotten.
curl -X DELETE 'https://app.useroster.work/api/workspaces/string/known-contacts/string'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.
Audit trail GET
Only people who manage the workspace (owners, and the role that can invite people) can read it; anyone else gets 403. Every change to how the workspace is set up, newest first, by whoever made it: a member (`member`), a hire (`hire`), Roster itself (`system`), the assistant (`assistant`) or an API token (`api_token`). Hires, their instructions, hours, tools, notebooks, responsibilities and follow-ups; skills; connections; departments, seats and goals; approvals decided; members, roles and invitations; workspace settings; seats. `action` is stable and dotted (`hire.renamed`, `note.added`); filter by one, or by everything about one kind of thing (`action=hire`). `changes` holds only the fields that changed, as `{ from, to }`, with credentials shown as `[redacted]`. `summary` is the change in one sentence and `sentence` the same in parts, the actor and the target marked so they can be linked. `requestId` ties together changes made by one request or one piece of a hire's work. Pass `next` back as `cursor` for older changes.