For the complete documentation index, see llms.txt. This page is also available as Markdown.

Ticket type

A ticket type says what kind of request a ticket is — an incident, a question, a change. Types are defined per tenant, identified by their name, and ordered for display by position.

They are seeded when a tenant is created and are read-only over the API for now.

List ticket types

get

Returns the tenant's ticket types — what kind of request a ticket is. position is the order they are meant to be shown in.

Filterable and sortablename, displayName, position, autoAssign, createdAt, updatedAt.

The list is read-only; the entries are seeded with the tenant.

Authorizations
AuthorizationstringRequired

Token issued by the central equipme authentication, sent as Bearer <token>.

Query parameters
filterstringOptional

JSON filter expression

searchstringOptional

Free-text term — no effect here

sortstringOptional

Comma-separated field:direction terms

fieldsstringOptional

Selection of fields and relations

Example: name,displayName
offsetintegerOptional

Number of entries to skip

Default: 0
limitintegerOptional

Page size, 1 to 100

Default: 100
Responses
200

OK

application/json
countintegerOptional
get/v1/ticket-types
GET /api/v1/ticket-types HTTP/1.1
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*
{
  "count": 1,
  "data": [
    {
      "assignmentContext": "text",
      "autoAssign": true,
      "createdAt": "2026-01-01T00:00:00.000Z",
      "displayName": "Incident",
      "name": "incident",
      "position": 1,
      "updatedAt": "2026-01-01T00:00:00.000Z"
    }
  ]
}

Last updated

Was this helpful?