Ticket Fields
/api/helpdesk/ticket-fields/{fieldKey}/selectOptions
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}/selectOptions
Static selectable values and their audience.
Parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
fieldKey |
path | string |
yes | field key |
Response
| Status | Content Type | Schema | Description |
|---|---|---|---|
200 |
application/json |
array<SelectOptionSetting> |
Successful response. |
Example Request
# Request
GET /api/helpdesk/ticket-fields/<fieldKey>/selectOptions HTTP/1.1
Accept: application/json
Authorization: Bearer <access-token>
# Response
HTTP/1.1 200 OK
Content-Type: application/json
[
{
"audience": "SUPPORTER_ONLY",
"metadata": [
"string"
],
"value": "string"
}
]
PUT /api/helpdesk/ticket-fields/{fieldKey}/selectOptions
Static selectable values and their audience.
Parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
fieldKey |
path | string |
yes | field key |
Request Body
| Content Type | Schema | Required | Description |
|---|---|---|---|
application/json |
array<SelectOptionSetting> |
yes |
Static selectable values and their audience. |
Response
| Status | Content Type | Schema | Description |
|---|---|---|---|
200 |
application/json |
array<SelectOptionSetting> |
Successful response. |
Example Request
# Request
PUT /api/helpdesk/ticket-fields/<fieldKey>/selectOptions HTTP/1.1
Accept: application/json
Authorization: Bearer <access-token>
Content-Type: application/json
[
{
"audience": "SUPPORTER_ONLY",
"metadata": [
"string"
],
"value": "string"
}
]
# Response
HTTP/1.1 200 OK
Content-Type: application/json
[
{
"audience": "SUPPORTER_ONLY",
"metadata": [
"string"
],
"value": "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.
SelectOptionSetting
| Property | Type | Required | Description |
|---|---|---|---|
audience |
string [SUPPORTER_ONLY, SUPPORTER_AND_ENDUSER] |
no | — |
metadata |
array<string> |
no | — |
value |
string |
no | — |
ApiError
| Property | Type | Required | Description |
|---|---|---|---|
status |
integer (int32) |
yes | — |
code |
string |
yes | — |
message |
string |
yes | — |
details |
array<object> |
no | — |