sensitive preserves the current flag, so clients that predate the field do not unmask answers by accident. Toggling sensitive changes whether playtest responses for its metadata_key are masked in the admin responses view from then on; answers already stored in player_metadata are not rewritten.curl --location --request PATCH 'https://api.lootlocker.io/admin/game//surveys/v1//questions/' \
--header 'Content-Type: application/json' \
--data '{
"question_text": "string",
"metadata_key": "string",
"field_type": "short_text",
"params": "string",
"required": true,
"sensitive": true,
"sort_order": 0
}'{
"id": "string",
"survey_id": "string",
"question_text": "string",
"metadata_key": "string",
"field_type": "string",
"params": {},
"required": true,
"sensitive": true,
"sort_order": 0,
"created_at": "string"
}