--- title: "Changes to Replace roster signup questions" method: PUT path: "/v2/roster/questionnaire" --- # Changes to Replace roster signup questions `PUT /v2/roster/questionnaire` > Every recorded change to this operation, newest first. ## Timeline Changed in 1 of 3 revisions. - **2026-09-09** `9ec0debedfc6`: 11 breaking, 3 warning, 25 info ## Changes - **2026-09-09** `9ec0debedfc6`: 11 breaking, 3 warning, 25 info - added the pattern `^\d{1,20}$` to the `query` request parameter `server_id` - the request property `questions` became required - the request property `questions/items/id` became required - the request property `questions/items/label` became required - the request property `questions/items/options` became required - the request property `questions/items/order` became required - the request property `questions/items/required` became required - the request property `questions/items/type` became required - request property `questions/items/order` list-of-types was narrowed by removing types `integer` from media type `application/json` - response property `affectedMemberCount` list-of-types was widened by adding types `number and string` to media type `application/json` of response `200` - response property `questionnaire/questions/items/order` list-of-types was widened by adding types `number and string` to media type `application/json` of response `200` - added the new `account` enum value to the `questionnaire/accountSelector/id` response property for the response status `200` - added the new `account` enum value to the `questionnaire/accountSelector/type` response property for the response status `200` - added the new `true` enum value to the `questionnaire/accountSelector/required` response property for the response status `200` - api operation id `dashboardRosterQuestionnaire` was added - the endpoint scheme security `BotToken` was added to the API - the endpoint scheme security `UserToken` was added to the API - the endpoint scheme security `ApiKeyAuth` was removed from the API - added the non-success response with the status `400` - added the non-success response with the status `401` - added the non-success response with the status `403` - added the non-success response with the status `404` - added the non-success response with the status `409` - added the non-success response with the status `413` - added the non-success response with the status `429` - added the non-success response with the status `503` - the response property `affectedMemberCount` became required for the status `200` - the response property `questionnaire` became required for the status `200` - the response property `questionnaire/accountSelector` became required for the status `200` - the response property `questionnaire/accountSelector/id` became required for the status `200` - the response property `questionnaire/accountSelector/required` became required for the status `200` - the response property `questionnaire/accountSelector/type` became required for the status `200` - the response property `questionnaire/questions` became required for the status `200` - the response property `questionnaire/questions/items/id` became required for the status `200` - the response property `questionnaire/questions/items/label` became required for the status `200` - the response property `questionnaire/questions/items/options` became required for the status `200` - the response property `questionnaire/questions/items/order` became required for the status `200` - the response property `questionnaire/questions/items/required` became required for the status `200` - the response property `questionnaire/questions/items/type` became required for the status `200` --- [Operation](https://skmtc.dev/clashk/apis/clashking-api/docs/v2/roster/questionnaire/put.md) - [API](https://skmtc.dev/clashk/apis/clashking-api.md) - [Page](https://skmtc.dev/clashk/apis/clashking-api/changes/v2/roster/questionnaire/put)