> ## 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 attachment configuration

> Check whether optional private image/PDF attachments are enabled, and read accepted file types and size limit.

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.

Check whether optional private image/PDF attachments are enabled, and read accepted file types and size limit.

Storage is optional. When disabled, this operation still returns configuration with enabled:false; other attachment operations are unavailable.

MCP clients can use [`get_attachment_config`](https://www.mill.fyi/mcp-reference/get_attachment_config) 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/attachments/config
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/attachments/config:
    get:
      tags:
        - Attachments
      summary: Read attachment configuration
      description: >-
        Check whether optional private image/PDF attachments are enabled, and
        read accepted file types and size limit.


        Storage is optional. When disabled, this operation still returns
        configuration with enabled:false; other attachment operations are
        unavailable.


        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_attachments_config
      responses:
        '200':
          description: >-
            Successful response. Examples are illustrative; field values vary by
            record.
          content:
            application/json:
              schema:
                type: object
                properties:
                  enabled:
                    type: boolean
                  maxBytes:
                    type: integer
                  contentTypes:
                    type: array
                    items:
                      type: string
                additionalProperties: true
                description: >-
                  Illustrative response shape. Fields can be absent in alternate
                  successful flows; see the operation description and example.
              example:
                enabled: true
                maxBytes: 20971520
                contentTypes:
                  - image/png
                  - image/jpeg
                  - image/webp
                  - image/gif
                  - application/pdf
        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.