---
title: "Changes to Refresh roster data or prepare role reconciliation"
method: POST
path: "/v2/roster/refresh-data"
---

# Changes to Refresh roster data or prepare role reconciliation

`POST /v2/roster/refresh-data`

> Every recorded change to this operation, newest first.

## Timeline

Changed in 1 of 3 revisions.

- **2026-09-09** `9ec0debedfc6`: 4 breaking, 4 warning, 24 info

## Changes

- **2026-09-09** `9ec0debedfc6`: 4 breaking, 4 warning, 24 info
  - added the pattern `^\d{1,20}$` to the `query` request parameter `server_id`
  - the request property `scope` became required
  - response property `failedPlayers` list-of-types was widened by adding types `number and string` to media type `application/json` of response `200`
  - response property `refreshedPlayers` list-of-types was widened by adding types `number and string` to media type `application/json` of response `200`
  - added the new `data` enum value to the `scope` response property for the response status `200`
  - added the new `payload_too_large` enum value to the `code` response property for the response status `429`
  - added the new `role` enum value to the `scope` response property for the response status `200`
  - added the new `unprocessable_entity` enum value to the `code` response property for the response status `429`
  - api operation id `dashboardRosterRefreshData` 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 `503`
  - the response property `code` became required for the status `429`
  - the response property `details/items/field` became required for the status `429`
  - the response property `details/items/message` became required for the status `429`
  - the response property `failedPlayers` became required for the status `200`
  - the response property `message` became required for the status `429`
  - the response property `refreshId` became required for the status `200`
  - the response property `refreshedAt` became required for the status `200`
  - the response property `refreshedPlayers` became required for the status `200`
  - the response property `reused` became required for the status `200`
  - the response property `scope` became required for the status `200`
  - the response property `status` became required for the status `200`
  - the `roleId` response's property pattern `^\d{1,20}$` was added for the status `200`
  - the `roleMemberUserIds/items/` response's property pattern `^\d{1,20}$` was added for the status `200`

---

[Operation](https://skmtc.dev/clashk/apis/clashking-api/docs/v2/roster/refresh-data/post.md) - [API](https://skmtc.dev/clashk/apis/clashking-api.md) - [Page](https://skmtc.dev/clashk/apis/clashking-api/changes/v2/roster/refresh-data/post)