Skip to main content
PUT
Update Entity Type Field

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

id
string
required

The ID of the entity type field to update.

Body

application/json
name
string | null

New display name. When provided and different from the current name, the field is renamed (key re-derived via slugify). Omit to leave unchanged.

dataType
enum<string> | null

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
enumOptions
EnumOptionInput · object[]

Required when data_type is changing to ENUM or MULTI_SELECT: the option set for the converted field.

description
string | null

Set or clear descriptive guidance without a schema migration. Omit to preserve. Send separately from a rename or data-type change.

Response

200 - application/json

Success

data
data · object

Reference to the staged migration applying the change. data.schema_migration_id is empty if the request was a no-op. At most one attribute may change per request. Description edits return an empty migration id immediately.