Itil Types
/api/helpdesk/itil-types/{itilTypeId}/messageType
Manages HelpDesk ITIL ticket types. Access requires either the general configuration permission or the HelpDesk ITIL-definition permission.
POST creates a request-local ITIL type, 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 types remain addressable. The configured default type cannot be deactivated and must remain available to all users.
GET /api/helpdesk/itil-types/{itilTypeId}/messageType
Mail routing after a new incident: 0 sends no mail, 1 sends to the ticket owner, 2 sends to the assigned resource, and 3 sends to the valid address in "messageEmail". Other values are rejected.
Parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
itilTypeId |
path | string |
yes | ITIL type identifier |
Response
| Status | Content Type | Schema | Description |
|---|---|---|---|
200 |
application/json |
integer (int32) |
Successful response. |
Example Request
# Request GET /api/helpdesk/itil-types/<itilTypeId>/messageType HTTP/1.1 Accept: application/json Authorization: Bearer <access-token> # Response HTTP/1.1 200 OK Content-Type: application/json 0
PUT /api/helpdesk/itil-types/{itilTypeId}/messageType
Mail routing after a new incident: 0 sends no mail, 1 sends to the ticket owner, 2 sends to the assigned resource, and 3 sends to the valid address in "messageEmail". Other values are rejected.
Parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
itilTypeId |
path | string |
yes | ITIL type identifier |
Request Body
| Content Type | Schema | Required | Description |
|---|---|---|---|
application/json |
integer (int32) |
yes |
Mail routing after a new incident: 0 sends no mail, 1 sends to the ticket owner, 2 sends to the assigned resource, and 3 sends to the valid address in "messageEmail". Other values are rejected. |
Response
| Status | Content Type | Schema | Description |
|---|---|---|---|
200 |
application/json |
integer (int32) |
Successful response. |
Example Request
# Request PUT /api/helpdesk/itil-types/<itilTypeId>/messageType HTTP/1.1 Accept: application/json Authorization: Bearer <access-token> Content-Type: application/json 0 # 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 | — |