person_list
Everyone who works here, with their exact name, email and mention, and what the company directory holds about them: their job title, their organization, who they report to, and when they started. Call this when somebody asks who a person is or who works here, and when a person hint was refused with a list of candidates to choose between. Do not call it to turn a fragment into a name before another call: person hints take the fragment as it was written and the server resolves it, so a name given partly or by a given name alone is already enough. requesterID names which of them is asking. `read` · v4
Authorization
memberToken The tools internkim uses inside a company, callable from outside it. A token belongs to a person, and every call runs as that person, so a token can never do more than its owner can.
The first token is made signed in, from the settings screen. After that a token makes its own
successors: POST /token for a new one, DELETE /token for the old one, so a script rotates
without a browser. A token can neither mint a rung above its own nor revoke itself.
Send Authorization: Bearer <token> on every request.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
curl -X POST "https://example.com/tools/person_list/invoke" \ -H "Content-Type: application/json" \ -d '{ "input": { "limit": 20 } }'{ "toolName": "person_list", "outcome": "succeeded", "selectedBackend": "device", "result": { "…": "the tool's own document" }}person_invite POST
Invite somebody to the company: it creates their account, gives them a temporary password to sign in with once, and puts them in the directory. Only an administrator invites people. The answer carries the temporary password, which is the only time it is readable, so pass it to whoever is bringing the person in. Requires approval; an account and an address are hard to take back. `workspace_write` · approval · v1
person_message_delete POST
Delete every message one person has written in the company messenger, in every conversation, for somebody leaving or asking to be forgotten. Only an administrator may. It reaches only a person still in the directory, so call it before person_withdraw. The answer counts what was deleted. Requires approval; deleted messages cannot be brought back. `destructive` · approval · v1