Documents
List comment threads, replies and resolves on an in-house Space document
Rows oldest first by seq: a thread is its first comment, replies and resolve/reopen rows carry parent: {object: "utterance", id: <thread id>}. Filter one thread with under, comments sent to the agent with to=agent and answered, by actor type, and page with after_seq (the last seq seen) and limit. Deleted comments vanish.
GET
/v1/space/documents/{document_id}/comments
curl -X GET "https://api.orchestor.io/v1/space/documents/%3Cdocument_id%3E/comments?limit=200" \ -H "Authorization: Bearer $API_KEY" \ -H "X-Workspace-ID: wks_abc123"{ "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>" } ], "has_more": true}Get your Orchestor API key
Create an API key in your workspace settings.
Authorizations
Authentication details
cookie
Query Parameters
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.
Example
"wks_abc123"Response
application/json