Impact level

Impact says how far a problem reaches — one person, a department, the whole organisation. Levels are defined per tenant, identified by their name and ranked by level: the higher, the wider the reach.

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

List impact levels

get

Returns the tenant's impact levels — how far a problem reaches. level ranks them, the higher the wider the reach; seeded as low (1), medium (2), high (3) and critical (4).

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-impacts

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

{
  "count": 1,
  "data": [
    {
      "color": "#f5a623",
      "createdAt": "2026-01-01T00:00:00.000Z",
      "displayName": "Abteilung",
      "level": 2,
      "name": "department",
      "updatedAt": "2026-01-01T00:00:00.000Z"
    }
  ]
}