# Ticket Part

Schema: #/components/schemas/ticket_part

Method: SCHEMA
Version: 2.18
Security: bearerAuth

## Schema fields:

  - `type` (string)
    Always ticket_part
    Example: ticket_part

  - `id` (string)
    The id representing the ticket part.
    Example: 3

  - `part_type` (string)
    The type of ticket part.
    Example: comment

  - `body` (string)
    The message body, which may contain HTML.
    Example: <p>Okay!</p>

  - `previous_ticket_state` (string)
    The previous state of the ticket.
    Enum: "submitted", "in_progress", "waiting_on_customer", "resolved"

  - `ticket_state` (string)
    The state of the ticket.
    Enum: "submitted", "in_progress", "waiting_on_customer", "resolved"

  - `created_at` (integer)
    The time the ticket part was created.
    Example: 1663597223

  - `updated_at` (integer)
    The last time the ticket part was updated.
    Example: 1663597260

  - `assigned_to` (object)
    reference to another object

  - `assigned_to.type` (string)
    Example: contact

  - `assigned_to.id` (string)
    Example: 1a2b3c

  - `admin_assignee_id` (integer)
    The id of the teammate that this ticket_part assigned the ticket to, or 0 if the part removed the teammate. Null or absent when the part did not change the teammate, including an unassignment that did not name which assignee it cleared. A bot is reported here, because assignment treats anything that is not a team as a teammate.
    Example: 991268013

  - `team_assignee_id` (integer)
    The id of the team that this ticket_part assigned the ticket to, or 0 if the part removed the team. Null or absent when the part did not change the team, including an unassignment that did not name which assignee it cleared. A part can assign a team and a teammate at the same time, for example when the team uses Round Robin distribution and the teammate is resolved inline. In that case assigned_to reports only the teammate, and these two fields report each assignee separately.
    Example: 5017691

  - `author` (object)
    The author that wrote or triggered the part. Can be a bot, admin, team or user.

  - `author.type` (string)
    The type of the author
    Enum: "admin", "bot", "team", "user"

  - `author.id` (string)
    The id of the author
    Example: 274

  - `author.name` (string)
    The name of the author
    Example: Operator

  - `author.email` (string)
    The email of the author
    Example: operator+abcd1234@intercom.io

  - `attachments` (array)
    A list of attachments for the part.

  - `attachments.type` (string)
    The type of attachment
    Example: upload

  - `attachments.name` (string)
    The name of the attachment
    Example: example.png

  - `attachments.url` (string)
    The URL of the attachment
    Example: https://picsum.photos/200/300

  - `attachments.content_type` (string)
    The content type of the attachment
    Example: image/png

  - `attachments.filesize` (integer)
    The size of the attachment
    Example: 100

  - `attachments.width` (integer)
    The width of the attachment
    Example: 100

  - `attachments.height` (integer)
    The height of the attachment
    Example: 100

  - `external_id` (string)
    The external id of the ticket part
    Example: abcd1234

  - `redacted` (boolean)
    Whether or not the ticket part has been redacted.
    Example: false

  - `app_package_code` (string)
    The app package code if this part was created via API. Note this field won't show if the part was not created via API.
    Example: text-integration

  - `translations` (object)
    A map of the reply text keyed by locale code. Backs the `ticket.admin.replied.translated` webhook topic. `original` holds the locale code the reply was written in, when it is known; every other key holds the reply translated into that locale.
    Example: {"original":"en","en":"<p>Hello</p>","fr":"<p>Bonjour</p>"}

  - `translations.original` (string)
    The locale code identifying the language the reply was originally written in.
    Example: en

  - `updated_attribute_data` (object)
    The updated attribute data of the ticket part. Only present for attribute update parts.

  - `updated_attribute_data.attribute` (object, required)
    Information about the attribute that was updated.

  - `updated_attribute_data.attribute.type` (string, required)
    The type of the object. Always 'attribute'.
    Enum: "attribute"

  - `updated_attribute_data.attribute.id` (string, required)
    The unique identifier of the attribute.
    Example: 7

  - `updated_attribute_data.attribute.label` (string, required)
    The human-readable name of the attribute.
    Example: Progress

  - `updated_attribute_data.value` (object, required)
    The new value of the attribute.

  - `updated_attribute_data.value.type` (string, required)
    The type of the object. Always 'value'.
    Enum: "value"

  - `updated_attribute_data.value.id` (any, required)

  - `updated_attribute_data.value.label` (any, required)

