Skip to main content
POST
Create Custom Field Option

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 create the custom field definition on.

Body

application/json
ticketType
enum<string>

The ticket type the field belongs to. Each ticket type carries its own field schema — a field created on REQUEST does not exist on JOURNEY.

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 | null

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

fieldName
string

Display name of the field, e.g. "System". Must be unique within the ticket type's schema.

dataType
enum<string>
Available options:
DATA_TYPE_UNSPECIFIED,
TEXT,
NUMBER,
BOOL,
TIMESTAMP,
ENUM,
ENTITY_REF,
USER_REF,
UNIQUE,
MULTI_SELECT,
FILE,
TICKET_REF
enumOptions
EnumOptionInput · object[]

Required for ENUM and MULTI_SELECT, rejected for every other data type. Each option must set both value and display_name.

sectionName
string

Group the field under a named section, creating the section on first reference. Omit to leave the field unsectioned (the Overview tab).

hidden
boolean

Create the field default-hidden: excluded from ticket-view field groups and list-view columns/filters, but still readable and writable.

Response

200 - application/json

Success

data
data · object

The created definition, shaped like the items ListCustomFieldOptions returns: field populated, field_value empty.