Your game
The game the key belongs to: its owned analytics and its players’ feedback. There is no id to pass; no other game’s data is readable with the key.
- GETYour game’s analytics
/game/analyticsThe key’s game’s owned analytics by UTC day, as the studio panel shows them: one series per metric and breakdown, oldest day first. A value Roblox has not given is left out, never 0. - GETYour game’s analytics by slice
/game/breakdownsThe key’s game’s daily breakdowns (platform, country, age group, acquisition source) as the studio panel shows them, with the read’s state. - GETYour game’s feedback themes
/game/feedback/themesThe key’s game’s feedback grouped into themes (its categories until text themes are found), each with its statuses and its count per week. - GETYour game’s feedback
/game/feedbackWhat the key’s game’s players sent, newest first, with how much there is of each category and status. The text is as the player wrote it: filter it before a player sees it. - POSTSend a player’s progress to another studio game
/game/transfersStores the fields the key’s game chose (a JSON object, at most 15360 bytes) for one player, for the target studio game to claim within 30 days. Call it when the player asks to move their progress, never on join. Sending again before the claim replaces the data; once claimed, the same player cannot be sent to that game again (409). The target must have a platform key of its own. No Open Cloud access and no key permission: the games hand the data over themselves (ADR-0075). - POSTClaim a player’s progress from another studio game
/game/transfers/claimAnswers the data another studio game sent to the key’s game for this player, and marks it claimed, once: a second claim finds nothing. Call it when the player accepts the transfer, then apply the data and save it. Send the same `claimKey` on every try of one claim: a retry whose first answer was lost gets the same transfer again. Transfers older than 30 days are not answered. - POSTBan a player in every studio game
/game/bansOptional: applies one ban to every studio game whose group key happens to have `universe.user-restriction:write` (Open Cloud user restrictions). The platform never asks for that permission; a game whose group key lacks it is skipped and says so. The ban is recorded for the studio’s owners, who can undo it in the panel. The answer says, for each studio game, whether the ban was applied, failed or skipped, and why. A key may make 20 an hour, beyond its per-minute limit (429 after that). - POSTRecord a release
/game/releasesRecords a release of the key’s game in its release log, where the studio panel, the MCP and the update suggestions read it. The title is its identity: the same title again answers the release already recorded (200), so a re-run records nothing new. Kinds: update, hotfix, event; a launch needs the game’s signed contract and is recorded in the panel.