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

Urgency level

Urgency says how soon a ticket needs an answer. Levels are defined per tenant, identified by their name and ranked by level: the higher, the more pressing.

Together with impact, urgency decides a ticket's priority.

List urgency levels

get

Returns the tenant's urgency levels — how soon a ticket needs an answer. level ranks them, the higher the more pressing; seeded as low (1), medium (2), high (3) and critical (4).

Filterable and sortablename, 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
get/v1/ticket-urgencies
GET /api/v1/ticket-urgencies 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"
    }
  ]
}

Last updated

Was this helpful?