PATCH
/api/public/v1/customer-custom-fields/{customFieldId}

Update a customer custom field

Update label, placeholder, options, required flag, or display order.

Required scope

The access token must carry this scope. A token missing it gets 403 Forbidden. Grant them to an API client under Dev Tools → API, to an assistant or CLI sign-in when you approve or edit it under Dev Tools, and to a teammate under Employee → Permissions.

customer:custom-fields:write

Path Parameters

NameTypeRequiredDescription
customFieldIdstringRequiredCustom field ID.

Request Body

PropertyTypeDescription
labelstringDisplay label.
placeholderstringPlaceholder text.
requiredbooleanWhether the field is required.
optionsarrayFor SELECT: array of { value, label }.
displayOrdernumberDisplay position.
PATCHExample request
curl
curl -X PATCH "https://www.pxb.app/api/public/v1/customer-custom-fields/{customFieldId}" \
  -H "Authorization: Bearer your_access_token" \
  -H "Content-Type: application/json" \
  -d '{
    "required": true
  }'
200Example response
json
{
  "message": "Customer custom field updated successfully!",
  "content": {
    "customField": {
      "id": "cf_1"
    }
  }
}

In the console

The same thing done by hand, for anyone comparing the API against the screen they already use.

xRM → Accounts → Custom fields
/xrm
  1. Open the Custom fields dialog from the accounts table header.
  2. Edit an existing field.