Comment on words of an in-house Space document, or reply in a thread
A thread anchors on words: parent: {object: "node", anchor: {kind: "find", text: "<3–6 words exactly as written>", nth?, parent_id?}}; without anchor it is a note on the whole document. One mark of a chart or one box of a diagram: anchor: {kind: "element", block_id: "<block id>", element: "datum:<x>" | "datum:<x>|<series>" | "node:<id>"} (element_none when it is not there). A reply names the thread: parent: {object: "utterance", id: "<thread id>"}. to: ["agent"] sends it to the agent. Limits: 1000 threads a document (resolved ones count), 100 comments a thread, 4096-byte bodies (too_many, row_too_large; nothing written).
curl -X POST "https://api.orchestor.io/v1/space/documents/%3Cdocument_id%3E/comments" \ -H "Authorization: Bearer $API_KEY" \ -H "X-Workspace-ID: wks_abc123" \ -H "Content-Type: application/json" \ -d '{ "body": "string", "parent": { "object": "node" }, "to": []}'{ "data": { "actor": { "id": "<string>", "name": "<string>", "type": "<string>" }, "answered": true, "body": "<string>", "created_at": "2026-01-01T00:00:00Z", "document_id": "<string>", "edits": [ 0 ], "id": "<string>", "kind": "comment", "parent": { "anchor": { "block_id": "<string>", "detached": true, "element": null, "end": "<string>", "start": "<string>", "text": "<string>" }, "id": "<string>", "object": "node" }, "resolved": true, "seq": 0, "to": [ "agent" ], "updated_at": "2026-01-01T00:00:00Z", "workspace_id": "<string>" }}Get your Orchestor API key
Create an API key in your workspace settings.
Authorizations
Authentication details
Headers
Workspace to access. With a workspace-scoped API key, the server derives this value from the key, so the header is optional. If supplied, it must match the credential workspace or the request returns 403 workspace_mismatch. For interactive session requests, supply this header to select a workspace where you are a member. A project ID cannot be used as a workspace ID.
"wks_abc123"