# Admin Reply on ticket

Schema: #/components/schemas/admin_reply_ticket_request

Method: SCHEMA
Version: 2.18
Security: bearerAuth

## Schema fields:

  - `message_type` (string, required)
    The type of reply. Tracker tickets and back-office tickets that are not shared with the customer do not support `comment`; use `note` instead.
    Enum: "comment", "note", "quick_reply"

  - `type` (string, required)
    Enum: "admin"

  - `body` (string)
    The text body of the reply. Notes accept some HTML formatting. Must be present for comment and note message types.
    Example: Hello there!

  - `admin_id` (string, required)
    The id of the admin who is authoring the comment.
    Example: 3156780

  - `created_at` (integer)
    The time the reply was created. If not provided, the current time will be used.
    Example: 1590000000

  - `reply_options` (array)
    The quick reply options to display. Must be present for quick_reply message types.

  - `reply_options.text` (string, required)
    The text to display in this quick reply option.

  - `reply_options.uuid` (string, required)
    A unique identifier for this quick reply option. This value will be available within the metadata of the comment ticket part that is created when a user clicks on this reply option.

  - `attachment_urls` (array)
    A list of image URLs that will be added as attachments. You can include up to 10 URLs.

  - `attachment_files` (array)
    A list of files that will be added as attachments. You can include up to 10 files. If both attachment_files and attachment_urls are provided, attachment_files takes precedence.

  - `attachment_files.content_type` (string)
    The content type of the file
    Example: application/json

  - `attachment_files.data` (string)
    The base64 encoded file data.
    Example: ewogICJ0ZXN0IjogMQp9

  - `attachment_files.name` (string)
    The name of the file.
    Example: test.json

  - `cross_post` (boolean)
    If set to true, the note will be cross-posted to all linked conversations. Only applicable to note message types on back-office tickets.
    Example: true

