Tickets

Tickets are the central work records and the parent of mail messages, appointments, and time records.

Ticket fields and identifiers

The {ticket} path parameter accepts a record ID or external identifier. Identifiers are opaque strings assigned by the source system. Tickets also participate in the provider custom-field system: import provider fields for the ticket model and send the resulting grouped additional data.

Retrieve ticket.schema.json for the current native request fields and constraints.

List tickets

Required scope: tickets:read. The standard list supports shared filters, relations, limit, and opt-in perPage pagination.

Query tickets

Required scope: tickets:read. The query supports table-layout fields and ticket filters. Pagination belongs in the JSON body, for example page and per_page.

Create a ticket

Required scope: tickets:write. Send fields accepted by the current ticket request schema. Relationships such as contact, address, users, device, contract, and contract option must reference records visible to the tenant.

Get a ticket

Required scope: tickets:read.

Update a ticket

Required scope: tickets:write. PUT is also registered.

Delete a ticket

Required scope: tickets:write. Returns 204 No Content on success.