dataroom_share_delete
Company dataroom: Revoke a data room share by its exact shareID from dataroom_get. Other active grants still apply. Already downloaded files cannot be recalled; existing signed URLs expire within ten minutes. `workspace_write` · approval · v1
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/dataroom_share_delete/invoke" \ -H "Content-Type: application/json" \ -d '{ "input": { "shareID": "…" } }'{ "toolName": "dataroom_share_delete", "outcome": "succeeded", "selectedBackend": "device", "effects": [ { "objectType": "dataroom", "effect": "created", "id": "7a93de11-…" } ], "result": { "…": "the tool's own document" }}dataroom_share_add POST
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
Read the existing work-history view as a company administrator GET
Read host diagnostics through the same execution records, event ledger, model exchanges, turn inputs, connector events, service logs and request metrics as the work-history web page. Only a company administrator may ask. Use recorded IDs for detail views. This reads existing evidence and executes no commands supplied by the caller.