Priorities
/api/helpdesk/priorities/{priorityId}/icon
Manages HelpDesk ticket priorities. Access requires either the general configuration permission or the HelpDesk template-definition permission.
POST creates a request-local priority, applies the supplied writable properties, validates it, and persists it. PUT and PATCH use the same validation. DELETE and active=false perform a soft deactivation; inactive priorities remain addressable.
The configured default priority and priorities referenced by active locations or user classes cannot be deactivated.
GET /api/helpdesk/priorities/{priorityId}/icon
Optional relative name of an existing priority icon. This property only stores the name; it does not upload or delete an icon file.
Parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
priorityId |
path | string |
yes | priority identifier |
Response
| Status | Content Type | Schema | Description |
|---|---|---|---|
200 |
application/json |
string |
Successful response. |
Example Request
# Request GET /api/helpdesk/priorities/<priorityId>/icon HTTP/1.1 Accept: application/json Authorization: Bearer <access-token> # Response HTTP/1.1 200 OK Content-Type: application/json "string"
PUT /api/helpdesk/priorities/{priorityId}/icon
Optional relative name of an existing priority icon. This property only stores the name; it does not upload or delete an icon file.
Parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
priorityId |
path | string |
yes | priority identifier |
Request Body
| Content Type | Schema | Required | Description |
|---|---|---|---|
application/json |
string |
yes |
Optional relative name of an existing priority icon. This property only stores the name; it does not upload or delete an icon file. |
Response
| Status | Content Type | Schema | Description |
|---|---|---|---|
200 |
application/json |
string |
Successful response. |
Example Request
# Request PUT /api/helpdesk/priorities/<priorityId>/icon HTTP/1.1 Accept: application/json Authorization: Bearer <access-token> Content-Type: application/json "string" # Response HTTP/1.1 200 OK Content-Type: application/json "string"
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 | — |