internkim
APIEvery endpointTask

task_update

Update explicit fields on an existing task, including who takes part in it, when canUpdate in task_list says the caller may change it. Classification fields use registeredLabels from task_list: business is a workspace label, while organizationHint and opportunityHint link CRM records. Choose classification values from those labels and the work context when the requester delegates that judgment. taskHint is the exact task ID or exact task title from a task_list result, resolved server-side to the canonical task; use task_list first when neither is known. At least one mutable field is required. `workspace_write` · v6

POST
/tools/task_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/task_update/invoke" \  -H "Content-Type: application/json" \  -d '{    "input": {      "taskHint": "draft the quarterly report",      "endsAt": "2026-09-05",      "participantPersonHints": [        "Sample Lee",        "Example Park"      ],      "size": "M"    }  }'

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