> ## Documentation Index
> Fetch the complete documentation index at: https://www.mill.fyi/llms.txt
> Use this file to discover all available pages before exploring further.

# List comments and replies

> 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.

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`](https://www.mill.fyi/mcp-reference/list_comments) for this operation.

[Request conventions](https://www.mill.fyi/api-reference/overview.md) · [API keys](https://www.mill.fyi/api-keys.md) · [MCP connections](https://www.mill.fyi/mcp-connections.md)


## OpenAPI

````yaml api-reference/openapi.json GET /api/tasks/{taskId}/comments
openapi: 3.1.0
info:
  title: Mill HTTP API
  version: 1.0.6
  description: >-
    All registered task-board, account, OAuth, MCP transport and health
    operations. MCP tool schemas come from runtime validators; account
    operations follow their server handlers. Example data is fictional.
    Generation imports routes without issuing requests or connecting to a
    database.
servers:
  - url: https://mill-api.example.com
security: []
paths:
  /api/tasks/{taskId}/comments:
    get:
      tags:
        - Comments and activity
      summary: List comments and replies
      description: >-
        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`.


        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.
      operationId: get_api_tasks_by_taskId_comments
      parameters:
        - name: taskId
          in: path
          required: true
          schema:
            type: string
            format: uuid
          description: >-
            The taskId from the corresponding list, record or authorization
            response.
        - name: parentId
          in: query
          required: false
          schema:
            anyOf:
              - type: string
                format: uuid
                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)$
              - type: string
                const: root
          description: JSON value
        - name: limit
          in: query
          required: false
          schema:
            type: integer
            minimum: 1
            maximum: 100
          description: integer
        - name: cursor
          in: query
          required: false
          schema:
            type: string
            maxLength: 2048
          description: string
      responses:
        '200':
          description: >-
            Successful response. Examples are illustrative; field values vary by
            record.
          content:
            application/json:
              schema:
                type: object
                properties:
                  items:
                    type: array
                    items:
                      type: object
                      properties:
                        id:
                          type: string
                        taskId:
                          type: string
                        parentId:
                          type:
                            - string
                            - 'null'
                        replyCount:
                          type: integer
                        authorId:
                          type: string
                        authorKind:
                          type: string
                        authorName:
                          type: string
                        body:
                          type: string
                        version:
                          type: integer
                        createdAt:
                          type: string
                        updatedAt:
                          type: string
                      additionalProperties: true
                  hasMore:
                    type: boolean
                  nextCursor:
                    type:
                      - string
                      - 'null'
                additionalProperties: true
                description: >-
                  Illustrative response shape. Fields can be absent in alternate
                  successful flows; see the operation description and example.
              example:
                items:
                  - id: 33333333-3333-4333-8333-333333333333
                    taskId: 22222222-2222-4222-8222-222222222222
                    parentId: null
                    replyCount: 0
                    authorId: 66666666-6666-4666-8666-666666666666
                    authorKind: human
                    authorName: Alex Morgan
                    body: The restore check passed.
                    version: 1
                    createdAt: '2027-01-18T09:30:00.000Z'
                    updatedAt: '2027-01-18T09:30:00.000Z'
                hasMore: false
                nextCursor: null
        default:
          description: >-
            Request failure. Inspect code, message and requestId; respect
            Retry-After on HTTP 429.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - bearerAuth: []
        - sessionCookie: []
components:
  schemas:
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
            - requestId
          properties:
            code:
              type: string
            message:
              type: string
            requestId:
              type: string
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: Personal or team Mill REST API key
    sessionCookie:
      type: apiKey
      in: cookie
      name: mill_session
      description: >-
        Signed-in human browser session; mutation requests also need the exact
        UI Origin

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.