Entity Type API
Update Entity Type Field
Update an entity type field: set its description, rename it (set name), or change its data type (set data_type, plus enum_options when the new type is ENUM/MULTI_SELECT). At most one attribute may change per request. Description edits apply immediately and return an empty schema_migration_id; an empty description clears it. Rename and data-type changes return schema_migration_id, which you poll via Get Schema Migration to track completion.
PUT
Update Entity Type Field
Authentication and permissions
Token requirements: User-based token (OAuth) or Organization-scoped API key or Workspace-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. Workspace keys must allow every workspace checked by the request. OAuth access depends on the user’s roles and resource access.
Authorizations
Body
application/json
New data type. When provided and different from the current type, the field's type is changed and existing values are converted. Omit to leave unchanged.
Available options:
DATA_TYPE_UNSPECIFIED, TEXT, NUMBER, BOOL, TIMESTAMP, ENUM, ENTITY_REF, USER_REF, UNIQUE, MULTI_SELECT, FILE, TICKET_REF, TIMESTAMP_RANGE, GROUP_REF 
