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

# Read task activity

> Read task and attachment activity, including who made each change. Comment and reply actions are not included.

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 task and attachment activity, including who made each change. Comment and reply actions are not included.

Task and attachment changes are recorded; comment and reply events are excluded, including historical comment rows. Activity identifies the responsible actor and, on new records, connection type and request ID.

MCP clients can use [`get_activity`](https://www.mill.fyi/mcp-reference/get_activity) 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}/activity
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}/activity:
    get:
      tags:
        - Comments and activity
      summary: Read task activity
      description: >-
        Read task and attachment activity, including who made each change.
        Comment and reply actions are not included.


        Task and attachment changes are recorded; comment and reply events are
        excluded, including historical comment rows. Activity identifies the
        responsible actor and, on new records, connection type and request ID.


        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_activity
      parameters:
        - name: taskId
          in: path
          required: true
          schema:
            type: string
            format: uuid
          description: >-
            The taskId from the corresponding list, record or authorization
            response.
        - 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
                        boardId:
                          type: string
                        actorId:
                          type: string
                        actorName:
                          type: string
                        actorKind:
                          type: string
                        action:
                          type: string
                        detail:
                          type: object
                          properties:
                            fields:
                              type: array
                              items:
                                type: string
                            connection:
                              type: object
                              properties:
                                type:
                                  type: string
                                requestId:
                                  type: string
                              additionalProperties: true
                          additionalProperties: true
                        createdAt:
                          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: 77777777-7777-4777-8777-777777777777
                    taskId: 22222222-2222-4222-8222-222222222222
                    boardId: 11111111-1111-4111-8111-111111111111
                    actorId: 66666666-6666-4666-8666-666666666666
                    actorName: Alex Morgan
                    actorKind: human
                    action: task.updated
                    detail:
                      fields:
                        - priority
                      connection:
                        type: session
                        requestId: example-request-001
                    createdAt: '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.