Delete a custom field
/settings/user-profile/custom-fields/{custom_field_id}Deletes a custom field definition.
Only the definition is removed. Values that users have already filled in for this field are retained but are no longer returned with the user's custom field values.
Autonomous mode: the API credential secret, sent as a bearer token. Credential secrets are identified by a fixed prefix.
In: header
Path Parameters
Public ID of the custom field, prefixed with cfd_.
Header Parameters
Client-generated key that makes the request safe to retry. Must be 1 to 128 characters from [A-Za-z0-9._:-]. Optional on this operation; when sent, a malformed key returns idempotency_key_invalid, and repeating the request with the same key and the same body returns the stored result with Idempotent-Replayed: true.
Optional client-generated identifier of the request, up to 64 characters from [A-Za-z0-9._-]. Echoed back in the response and recorded in the request log; it never replaces the server-generated X-Request-Id.
length <= 64Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/settings/user-profile/custom-fields/string"Update a custom field PATCH
Updates a custom field definition. Fields omitted from the request keep their current values. The `type` of a field cannot be changed once users have filled in values for it. Such requests return the `state_conflict` error code. To avoid overwriting a newer version, send the `ETag` returned by the retrieve operation in the `If-Match` header.
Gamification2
Next Page