internkim
APIEvery endpointCompany

company_document_register

Register a company document in the document ledger and, for kind=issued, receive the official document number to print in the document plus the storage directory to save the final file in. Call BEFORE rendering an official document so the number appears in it. Always include a 2-3 sentence summary of the document's key terms (parties, amounts, dates) so later questions can be answered without re-reading the file. A document filed in the data room names its categoryCode, date and hash, and its files are uploaded with company_document_upload once it is registered; one that replaces an older document names it with supersedesHint instead of editing it. `workspace_write` · v2

POST
/tools/company_document_register/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/company_document_register/invoke" \  -H "Content-Type: application/json" \  -d '{    "input": {      "documentType": "…",      "summary": "…",      "title": "draft the quarterly report",      "status": "planned"    }  }'

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