Skip to main content
GET
List Custom Field Options

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

team_id
string
required

The ID of the team to list custom field options for.

Query Parameters

ticketType
enum<string>

The ticket type to list custom field options for.

Available options:
TICKET_TYPE_UNSPECIFIED,
TICKET_TYPE_REQUEST,
TICKET_TYPE_TASK,
TICKET_TYPE_MAJOR_INCIDENT,
TICKET_TYPE_CONVERSATION,
TICKET_TYPE_JOURNEY,
TICKET_TYPE_INCIDENT,
TICKET_TYPE_CHANGE,
TICKET_TYPE_CUSTOM,
TICKET_TYPE_PROBLEM
ticketSubtype
string

Required for CHANGE tickets — each subtype (normal, standard, emergency, custom) has its own field schema. Omit for non-change types.

Response

200 - application/json

Success

data
data · object