Create Custom Field Option
Create a custom field definition on a team’s ticket type. Each ticket type has its own field schema, so a field created on REQUEST does not exist on JOURNEY. ENUM and MULTI_SELECT fields require enum_options; every other data type rejects them. Use this before setting values on tickets when the field does not exist yet.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The ID of the team to create the custom field definition on.
Body
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.
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 Required for CHANGE tickets — each subtype (normal, standard, emergency, custom) has its own field schema. Omit for non-change types.
Display name of the field, e.g. "System". Must be unique within the ticket type's schema.
DATA_TYPE_UNSPECIFIED, TEXT, NUMBER, BOOL, TIMESTAMP, ENUM, ENTITY_REF, USER_REF, UNIQUE, MULTI_SELECT, FILE Required for ENUM and MULTI_SELECT, rejected for every other data type. Each option must set both value and display_name.
Group the field under a named section, creating the section on first reference. Omit to leave the field unsectioned (the Overview tab).
Create the field default-hidden: excluded from ticket-view field groups and list-view columns/filters, but still readable and writable.
Response
Success
The created definition, shaped like the items ListCustomFieldOptions
returns: field populated, field_value empty.

