Ticket Fields
/api/helpdesk/ticket-fields/{fieldKey}/enduserEditable
Exposes registered, open, and user-created HelpDesk ticket-field settings.
The endpoint is intentionally request-local: annotation setters only change this object, while commit reconstructs a complete manager property map and delegates validation and persistence to TicketFieldSettingsManager. A normal DELETE operation is not exposed. Hiding a field is represented by FIELD_VISIBILITY#HIDDEN; permanent deletion is available only through the confirmation-protected action.
GET /api/helpdesk/ticket-fields/{fieldKey}/enduserEditable
End-user editability and mandatory state.
Parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
fieldKey |
path | string |
yes | field key |
Response
| Status | Content Type | Schema | Description |
|---|---|---|---|
200 |
application/json |
string [REQUIRED, VISIBLE, HIDDEN] |
Successful response. |
Example Request
# Request GET /api/helpdesk/ticket-fields/<fieldKey>/enduserEditable HTTP/1.1 Accept: application/json Authorization: Bearer <access-token> # Response HTTP/1.1 200 OK Content-Type: application/json "REQUIRED"
PUT /api/helpdesk/ticket-fields/{fieldKey}/enduserEditable
End-user editability and mandatory state.
Parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
fieldKey |
path | string |
yes | field key |
Request Body
| Content Type | Schema | Required | Description |
|---|---|---|---|
application/json |
string [REQUIRED, VISIBLE, HIDDEN] |
yes |
End-user editability and mandatory state. |
Response
| Status | Content Type | Schema | Description |
|---|---|---|---|
200 |
application/json |
string [REQUIRED, VISIBLE, HIDDEN] |
Successful response. |
Example Request
# Request PUT /api/helpdesk/ticket-fields/<fieldKey>/enduserEditable HTTP/1.1 Accept: application/json Authorization: Bearer <access-token> Content-Type: application/json "REQUIRED" # Response HTTP/1.1 200 OK Content-Type: application/json "REQUIRED"
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 | — |