⚠️ Experimental endpoint — not yet a stable contract. This action ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.

Set the applicable custom field values of a user without changing any other user properties. This action requires permission to view the user and the Users.update-custom-fields permission.

Send a JSON object containing only the required customFields property. Query parameters and additional body properties are rejected. The customFields object may be empty. Omitted identifiers remain unchanged, while an explicit null clears the corresponding value. Every submitted identifier is validated against the user, the current custom field configuration and the acting administrator's access. Invalid request bodies or values and unknown or unusable submitted field identifiers return 422 validation errors, keyed as customFields.<identifier> for invalid identifiers. If custom fields are disabled for the tenant or users, the action returns 412 Precondition Failed. Neither rejection changes custom field values.