Skip to main content
tickets

Detail /tickets/{uuid}

Get one ticket by UUID (/tickets/{uuid}). Returns record with core fields, the initial message (as stored, usually HTML) and message_text (plain text), status, priority, type, departments, assignees, relations, CC fields, tags, dates, custom fields, and organization when applicable. The conversation is in /ticket_replies?filter[ticket]={uuid}, internal notes in /ticket_notes, the change history in /ticket_history and files in /tickets/{uuid}/files. Reference entities use UUIDs only.

GET
/tickets/{uuid}

Authorizations

Authorizationstringheaderrequired

API key (Bearer token) created in Setup → API & MCP.

Path Parameters

uuidstringrequired

Record identifier (uuid)

Query Parameters

fieldsstring[]query

Optional response field paths (dot notation for nested groups, e.g. billing_address.street; array fields are returned whole). Comma-separated string is also accepted. Identifier field is always included.

Response

application/json

Single record

recordobject

Fields enabled for this documentation instance (projection enabled: feature, option, subdomain, closures) plus account-level form field visibility. Role- and user-level field overrides are not applied here, so an API key whose staff user has such overrides may receive fewer fields. A disabled field is omitted from the response object entirely; a present key with a null value means the record simply has no value.

Still need help? Ask the team