# List comments for an appointment

Returns all appointment comments/alerts plus patient comments/alerts for the appointment's patient when the caller is authorized.

Endpoint: GET /integrations/v1/{domain}/appointments/{appointmentId}/comments
Version: v1
Security: Bearer

## Path parameters:

  - `domain` (string, required)
    Partner domain identifier. Your bearer token is scoped to one or more domains and requests outside that scope are rejected.
    Example: "acme"

  - `appointmentId` (string, required)
    Appointment identifier within the specified domain.
    Example: "A123456"

## Response 200 fields (application/json):

  - `guid` (string, required)
    Comment GUID.
    Example: "123"

  - `commentType` (string, required)
    Comment type. One of: AC (Appointment Comment), AA (Appointment Alert), PC (Patient Comment), PA (Patient Alert).
    Example: "Example commentType"

  - `appointmentId` (string)
    Appointment identifier for appointment comments; empty for patient-level comments.
    Example: "123"

  - `patientId` (string)
    Patient identifier associated with the comment when available.
    Example: "123"

  - `commentText` (string)
    Comment text.
    Example: "Example commentText"

  - `commentDateTime` (null,string)
    When the comment was created when available.
    Example: "2020-01-01T00:00:00Z"

  - `isAlert` (boolean)
    Whether this comment should be treated as an alert.
    Example: true

  - `commentBy` (any)
    Who created the comment when available.

  - `lastModifiedDateTime` (null,string)
    When the comment was last modified.
    Example: "2020-01-01T00:00:00Z"

  - `lastModifiedBy` (any)
    Who last modified the comment when available.

## Response 400 fields (application/problem+json):

  - `type` (null,string)
    Example: "Example type"

  - `title` (null,string)
    Example: "Example title"

  - `status` (null,integer,string)
    Example: 1

  - `detail` (null,string)
    Example: "Example detail"

  - `instance` (null,string)
    Example: "Example instance"

## Response 401 fields (application/problem+json):

  - `type` (null,string)
    Example: "Example type"

  - `title` (null,string)
    Example: "Example title"

  - `status` (null,integer,string)
    Example: 1

  - `detail` (null,string)
    Example: "Example detail"

  - `instance` (null,string)
    Example: "Example instance"

## Response 403 fields (application/problem+json):

  - `type` (null,string)
    Example: "Example type"

  - `title` (null,string)
    Example: "Example title"

  - `status` (null,integer,string)
    Example: 1

  - `detail` (null,string)
    Example: "Example detail"

  - `instance` (null,string)
    Example: "Example instance"

## Response 404 fields (application/problem+json):

  - `type` (null,string)
    Example: "Example type"

  - `title` (null,string)
    Example: "Example title"

  - `status` (null,integer,string)
    Example: 1

  - `detail` (null,string)
    Example: "Example detail"

  - `instance` (null,string)
    Example: "Example instance"

## Response 500 fields (application/problem+json):

  - `type` (null,string)
    Example: "Example type"

  - `title` (null,string)
    Example: "Example title"

  - `status` (null,integer,string)
    Example: 1

  - `detail` (null,string)
    Example: "Example detail"

  - `instance` (null,string)
    Example: "Example instance"