Classifications

/api/helpdesk/classifications/{classificationId}/id

Manages HelpDesk ticket classifications. Access requires either the general configuration permission or the HelpDesk template-definition permission.

POST creates a request-local classification, applies the supplied writable properties, validates it, and persists it with a server-generated identifier. PUT and PATCH use the same validation. DELETE and active=false perform a soft deactivation; inactive classifications remain addressable. The configured default classification cannot be deactivated.

GET /api/helpdesk/classifications/{classificationId}/id

Stable server-generated classification identifier. Read-only.

Parameters

Name	Location	Type	Required	Description
`classificationId`	path	`string`	yes	classification identifier

Response

Status	Content Type	Schema	Description
`200`	`application/json`	`integer (int32)`	Successful response.

Example Request

# Request
GET /api/helpdesk/classifications/<classificationId>/id HTTP/1.1
Accept: application/json
Authorization: Bearer <access-token>

# Response
HTTP/1.1 200 OK
Content-Type: application/json

0

Common Error Responses

The status codes 400, 403, 404, 405, 406, 409, 413, 415, and 500 use the same ApiError JSON error format:

{
    "status": 404,
    "code": "route_not_found",
    "message": "The requested API route does not exist.",
    "details": []
}

Schemas

Request and response schemas used on this page.

ApiError

Property	Type	Required	Description
`status`	`integer (int32)`	yes	—
`code`	`string`	yes	—
`message`	`string`	yes	—
`details`	`array<object>`	no	—