Priority

Priority says what to work on first. Levels are defined per tenant, identified by their name and ranked by level.

A priority is normally not chosen but derived: when a ticket's impact or urgency changes and both are then set, the priority is resolved from the tenant's impact × urgency matrix. Setting priorityName on a ticket overrides that, and the chosen priority is left alone as long as neither axis is touched again.

List priorities

get

Returns the tenant's priorities — what to work on first. level ranks them, the higher the more important; seeded as low (1), medium (2), high (3) and critical (4).

A ticket's priority is normally resolved from its impact and urgency rather than chosen directly.

Filterable and sortable — name, displayName, level, color, 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,level

offsetintegerOptional

Number of entries to skip

Default: 0

limitintegerOptional

Page size, 1 to 100

Default: 100

Responses

200

OK

application/json

countintegerOptional

400

Bad Request

application/json

401

Unauthorized

application/json

403

Forbidden

application/json

500

Internal Server Error

application/json

get/v1/ticket-priorities

GET /api/v1/ticket-priorities HTTP/1.1
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*

{
  "count": 1,
  "data": [
    {
      "color": "#d0021b",
      "createdAt": "2026-01-01T00:00:00.000Z",
      "displayName": "Hoch",
      "level": 3,
      "name": "high",
      "updatedAt": "2026-01-01T00:00:00.000Z"
    }
  ]
}