User Classes
/api/helpdesk/user-classes/{userClassId}/supervisorIds
Manages HelpDesk user classes and their supervisors. Access requires either the general configuration permission or the HelpDesk template-definition permission.
POST creates a request-local user class, applies the supplied writable properties, validates it, and persists it with a server-generated identifier. PUT and PATCH use the same validation. Supervisor assignments are persisted together with the class and are restored best-effort after a partial failure.
DELETE and active=false perform a soft deactivation. The configured default class and a class currently assigned to users cannot be deactivated.
GET /api/helpdesk/user-classes/{userClassId}/supervisorIds
Complete set of supervising HelpDesk user account identifiers. Each value must be an existing lowercase alphanumeric GUID string, for example "0123456789abcdefghijklmno". When supplied, this property replaces the complete supervisor set; an empty array removes all supervisors.
Parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
userClassId |
path | string |
yes | user-class identifier |
Response
| Status | Content Type | Schema | Description |
|---|---|---|---|
200 |
application/json |
array<string> |
Successful response. |
Example Request
# Request
GET /api/helpdesk/user-classes/<userClassId>/supervisorIds HTTP/1.1
Accept: application/json
Authorization: Bearer <access-token>
# Response
HTTP/1.1 200 OK
Content-Type: application/json
[
"8j4942vmqpkl9uipunqipno2r"
]
PUT /api/helpdesk/user-classes/{userClassId}/supervisorIds
Complete set of supervising HelpDesk user account identifiers. Each value must be an existing lowercase alphanumeric GUID string, for example "0123456789abcdefghijklmno". When supplied, this property replaces the complete supervisor set; an empty array removes all supervisors.
Parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
userClassId |
path | string |
yes | user-class identifier |
Request Body
| Content Type | Schema | Required | Description |
|---|---|---|---|
application/json |
array<string> |
yes |
Complete set of supervising HelpDesk user account identifiers. Each value must be an existing lowercase alphanumeric GUID string, for example "0123456789abcdefghijklmno". When supplied, this property replaces the complete supervisor set; an empty array removes all supervisors. |
Response
| Status | Content Type | Schema | Description |
|---|---|---|---|
200 |
application/json |
array<string> |
Successful response. |
Example Request
# Request
PUT /api/helpdesk/user-classes/<userClassId>/supervisorIds HTTP/1.1
Accept: application/json
Authorization: Bearer <access-token>
Content-Type: application/json
[
"e7hlamkvzzq2nmw6nw6yzzmo3"
]
# Response
HTTP/1.1 200 OK
Content-Type: application/json
[
"3x2w2gv1pt1inadslxajzc528"
]
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 | — |