Skip to main content
GET
Get Ticket Custom Field Values

Authentication and permissions

Token requirements: User-based token (OAuth) or Organization-scoped API key or Team-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Team keys must allow every team checked by the request. OAuth access depends on the user’s roles and resource access.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

ticket_id
string
required

The ID of the ticket to get custom field values for.

Response

200 - application/json

Success

Returns the ticket's custom-field schema for its (type, subtype) model, with current values where set. Unset fields still appear (field_value empty). When no values have ever been written the schema is still returned — resolved from the ticket row, same as the UI's GetCustomFieldOptionsForTicketType path.

customFields
CustomFieldValue · object[]
deprecatedFields
CustomFieldValue · object[]
customFieldGroups
CustomFieldGroup · object[]

Active custom fields grouped by their svstore entity_field_section. Use this when rendering one container per group on the UI; the existing custom_fields list is retained for flat-list consumers.