Skip to main content
GET
List comments and replies
Read access: a read-enabled personal or team REST API key, or a signed-in user. OAuth clients use the corresponding MCP tool through /mcp. Read comments on a task, newest first. Set parentId to root for top-level comments or a comment UUID for its direct replies. Omit it for all comments. Each comment includes parentId and replyCount; use the cursor within the same thread to load older comments. Omit parentId for a flat list, use root for top-level comments, or a same-task comment UUID for direct replies. Each thread has its own cursor. Replies collapse in the UI; the API returns parentId and direct replyCount. MCP clients can use list_comments for this operation. Request conventions · API keys · MCP connections

Authorizations

Authorization
string
header
required

Personal or team Mill REST API key

Path Parameters

taskId
string<uuid>
required

The taskId from the corresponding list, record or authorization response.

Query Parameters

parentId

JSON value

Pattern: ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$
limit
integer

integer

Required range: 1 <= x <= 100
cursor
string

string

Maximum string length: 2048

Response

Successful response. Examples are illustrative; field values vary by record.

Illustrative response shape. Fields can be absent in alternate successful flows; see the operation description and example.

items
object[]
hasMore
boolean
nextCursor
string | null