internkim
APIEvery endpointDataroom

dataroom_share_add

Company dataroom: Share live data room categories with someone outside the company by lending them what one circle reads: an external email or an explicitly public audience. Current and future documents in those categories become readable. Confirm the audience and scope first. Recipients must accept using their verified email; do not invite them as company members. Company members read through the circles they belong to, set with circle_member_update. Public publication is a distinct explicit request and never includes X. `workspace_write` · approval · v1

POST
/tools/dataroom_share_add/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/dataroom_share_add/invoke" \  -H "Content-Type: application/json" \  -d '{    "input": {      "circleID": "…",      "audience": "email"    }  }'

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