internkim
APIEvery endpointCircle

circle_update

Company circles: Create or edit a circle. id is its lowercase English name, such as sales-team, and never changes; name is what people read and is given only to a circle the company made, since the product names its default circles in every language. readableCategories names the data room categories its members read, and a parent grants all descendants. Members change access immediately, so read circle_list and confirm who is affected first. A circle confers no administrative or editing rights. `workspace_write` · approval · v1

POST
/tools/circle_update/invoke

Authorization

memberToken
AuthorizationBearer <token>

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/circle_update/invoke" \  -H "Content-Type: application/json" \  -d '{    "input": {      "id": "…",      "readableCategories": []    }  }'

{  "toolName": "circle_update",  "outcome": "succeeded",  "selectedBackend": "device",  "effects": [    {      "objectType": "circle",      "effect": "created",      "id": "7a93de11-…"    }  ],  "result": {    "…": "the tool's own document"  }}