POST /api/v2/imports/tickets

Default value: "application/json"

If true, any ticket created with a closed status bypasses the normal ticket lifecycle and will be created directly in your ticket archive

An id you can use to link Zendesk Support tickets to local records

An array of objects that represent agent or end users email CCs to add or delete from the ticket. See Setting email CCs

Valid values:

• "put"
• "delete"

An object explaining how the ticket was created. See the Via object reference

For some channels a source object gives more information about how or why the ticket or event was created

This tells you how the ticket or event was created

Read-only first comment on the ticket. When creating a ticket, use comment to set the description. See Description and first comment

The state of the ticket

Valid values:

• "open"
• "hold"
• "new"
• "pending"
• "closed"
• "solved"

The value of the subject field for this ticket

An array of objects that represent agent followers to add or delete from the ticket. See Setting followers

Valid values:

• "put"
• "delete"

The original recipient e-mail address of the ticket

The time the ticket was last updated (for historical imports)

The user who requested this ticket

The agent currently assigned to the ticket

Users to add as cc's when creating a ticket. See Setting Collaborators

The array of tags applied to this ticket

The time the ticket was solved (for historical imports)

The time the ticket was created (for historical imports)

The custom ticket status id of the ticket

Custom field values to set on the ticket. Each entry specifies a field ID and its value.

The ID of the custom field

The value to assign to the custom field. Type depends on the field configuration:

• Text/textarea: string
• Checkbox: boolean or "true"/"false" string
• Dropdown/tagger: string or array of strings (multi-select)
• Number/decimal: number or string representation
• Date: string (ISO 8601 format)

The conversation between requesters, collaborators, and agents

Describes how the object was created. See the Via object reference

For some channels a source object gives more information about how or why the ticket or event was created

This tells you how the ticket or event was created. Examples: "web", "mobile", "rule", "system"

true if a public comment; false if an internal note. The initial value set on ticket creation persists for any additional comment unless you change it

Internal flag for adding short URLs to the comment

System information (web client, IP address, etc.) and comment flags, if any. See Comment flags

The comment string value

Automatically assigned when the comment is created

The comment presented as plain text. See Bodies

The locale code to translate the comment body to.

Attachments, if any. See Attachment

The content type of the image. Example value: "image/png"

If true, the attachment is excluded from the attachment list and the attachment's URL can be referenced within the comment of a ticket. Default is false

The size of the image file in bytes

If true, the attachment has been deleted

The height of the image file in pixels. If height is unknown, returns null

A URL to access the attachment details

The width of the image file in pixels. If width is unknown, returns null

An array of attachment objects. Note that photo thumbnails do not have thumbnails

The content type of the image. Example value: "image/png"

If true, the attachment is excluded from the attachment list and the attachment's URL can be referenced within the comment of a ticket. Default is false

The size of the image file in bytes

If true, the attachment has been deleted

The height of the image file in pixels. If height is unknown, returns null

A URL to access the attachment details

The width of the image file in pixels. If width is unknown, returns null

If true, you can download an attachment flagged as malware. If false, you can't download such an attachment.

The URL the attachment image file has been mapped to

The name of the image file

A full URL where the attachment image file can be downloaded. The file may be hosted externally so take care not to inadvertently send Zendesk authentication credentials. See Working with url properties

Automatically assigned when created

The result of the malware scan. There is a delay between the time the attachment is uploaded and when the malware scan is completed. Usually the scan is done within a few seconds, but high load conditions can delay the scan results. Possible values: "malware_found", "malware_not_found", "failed_to_scan", "not_scanned"

If true, you can download an attachment flagged as malware. If false, you can't download such an attachment.

The URL the attachment image file has been mapped to

The name of the image file

A full URL where the attachment image file can be downloaded. The file may be hosted externally so take care not to inadvertently send Zendesk authentication credentials. See Working with url properties

Automatically assigned when created

The result of the malware scan. There is a delay between the time the attachment is uploaded and when the malware scan is completed. Usually the scan is done within a few seconds, but high load conditions can delay the scan results. Possible values: "malware_found", "malware_not_found", "failed_to_scan", "not_scanned"

The id of the comment author. If null or omitted on create, defaults to the authenticated user. See Author id

The id of the ticket audit record. See Show Audit

The comment string. See Bodies

Internal channel back identifier for the comment

Comment or VoiceComment. The JSON object for adding voice comments to tickets is different. See Adding voice comments to tickets

The comment formatted as HTML. See Bodies

List of tokens received from uploading files for comment attachments. The files are attached by creating or updating tickets with the tokens. See Attaching files in Tickets

The time the comment was created

Internal channel source identifier for the comment

The group this ticket is assigned to