Developer API changelog

What changed in the developer API and the Template's platform service, newest first: public docs and Try it, market reads, then feedback and game keys.

Building on the platform

The developer API is version 1: every route is under /developer/v1, and nothing has been removed or changed incompatibly since it began. Entries are newest first, dated by the day (UTC) the change was merged into the platform.

2026-11-04: bans applied once, a quieter cache

  • POST /developer/v1/game/bans takes an optional idempotencyKey. Send the same one on every try of one ban: a retry whose answer was lost gets the ban already recorded instead of a second one. Bans now reach every game at once and are recorded before any game is asked.

  • Feedback, transfers and bans no longer empty the platform's cached answers, so busy games keep everyone's reads fast.

2026-11-04: optional studio-wide bans

  • POST /developer/v1/game/bans bans a player in every studio game whose group key happens to have universe.user-restriction:write. The permission is optional: the platform never asks for it, and a game whose key lacks it is skipped with the reason in the answer. Owners see and undo bans in the panel.

2026-11-04: cross-game transfers

  • POST /developer/v1/game/transfers stores a player's progress (data, a JSON object up to 15 KB) for another studio game; POST /developer/v1/game/transfers/claim answers it to that game once; send the same claimKey on every try, so a retry whose answer was lost gets it again. Send when the player asks to move, claim when they accept: never on join. A claimed transfer cannot be sent again (409).

  • The 413 message is now The body is larger than the developer API accepts: the 16 KiB limit was always every route's, not only feedback's.

2026-11-04: limited items

  • GET /developer/v1/items/limiteds answers Roblox's limited items with their recent average price and Rolimon's value, demand, trend and projected, hyped and rare flags, stored every five minutes. Sort by value, rap or name; read up to 100 by ids; search by q. Thumbnails come from the engine: rbxthumb://type=Asset&id=<id>&w=150&h=150.

  • The Template's PlatformService.limiteds(query) reads it through the shared cache.

2026-11-04: an ETag on every read

  • /key, /key/usage and the /game/... reads now carry an ETag too, so If-None-Match gets a 304 with no body on every developer read, as on the market reads.

2026-11-04: breakdowns, feedback themes and key usage

  • GET /developer/v1/game/breakdowns answers the key's own game's daily breakdowns (range, metric, dimension) as the panel does.

  • GET /developer/v1/game/feedback/themes answers its feedback grouped into themes over weeks (from, to).

  • GET /developer/v1/key/usage answers the key's own requests over 24 hours and 7 days, by route and outcome; usage is null when the counts cannot be read.

  • The Template's staff Platform tab shows all three, read only.

2026-11-04: releases recorded with the key

  • POST /developer/v1/game/releases records an update, hotfix or event of the key's own game in its release log (title, notes, releasedAt, placeVersion). The same title again answers the release already recorded (200), so a re-run records nothing new; a launch stays a member's action in the panel.

  • The Template's publish-live workflow records each version it publishes, with its changelog notes, from the BLOCKOUT_API_KEY Actions secret.

2026-11-04: feedback by player

  • GET /developer/v1/game/feedback?player=<user id> answers only what that player sent, with counts and total for that player. The Template uses it to show a player their own sends and what became of them.

2026-11-03: the key's own game

  • GET /developer/v1/game/analytics answers the key's own game's owned analytics over 30d (the default), 90d or 365d: the same answer the panel's metrics for that game give.

  • GET /developer/v1/game/feedback answers the key's own game's feedback, newest first, with the panel's filters (category, status, from, to, q, offset, limit up to 50).

  • Neither takes an id: the key names the game, and no other game's data is readable with it. Neither is read-cached on the platform. Both count against the key and show in its usage on the Developer tab.

  • The Template's PlatformService.analytics and feedbackList, and its staff Platform tab, now read real data. The Template's unsupported reason is gone.

2026-10-27: public docs, the OpenAPI document and Try it

  • Public docs: this handbook is public at docs.blockoutgames.com, with nothing to sign in to.

  • OpenAPI 3.1: every route of /developer/v1 is described at docs.blockoutgames.com/openapi.json, and drawn as an interactive API reference. A test sends every example in it to the API.

  • Try it: the reference sends requests from your browser with a key you type. The panel's /developer/v1 answers CORS for https://docs.blockoutgames.com only. See Trying the API from the docs.

  • The Template is the SDK: the standalone BlockoutFeedback module is removed. A game sends feedback and reads the platform through the Template's platform service; a game not built on the Template calls the routes over HTTP (Sending feedback over HTTP).

2026-10-24: market reads, ids batching and key usage

Market reads were added to the developer API on 24 October 2026, after game keys and feedback.

A game's key can now read the market data the platform has stored, with the same answers the panel's own reads give, from the read cache. No read asks Roblox or starts tracking a game: an untracked game is 404.

GET /developer/v1/key

The game the key belongs to and its limit per minute. Reference.

GET /developer/v1/games

The tracked games list, with every filter the panel's Explore table has, and ids to read up to 100 games in one call. Reference.

GET /developer/v1/games/:id

One tracked game in full. Reference.

GET /developer/v1/games/:id/history

A game's players over 6 hours to all time. Reference.

GET /developer/v1/genres

Each first-level genre with its games and players. Reference.

GET /developer/v1/market

The market overview over 24 hours, 7 days or 30 days. Reference.

Key usage

The game's Developer tab counts the key's requests by route and outcome, per UTC hour, kept eight days. See A game's Developer tab.

Reads and feedback share the key's 120 requests a minute and the 1,200 for every key together. Answers carry ETag and X-Cache; If-None-Match gets a 304.

2026-10-23: the Template's platform service

PlatformService was added to the Blockout Roblox Template on its feature/platform-api branch, off by default behind Config/Features.platform: every read through a MemoryStore cache all servers share, feedback with one idempotency key across retries, the Feedback window with per-player limits, and the staff platform command. See The Template's platform service and Inside the Template's platform service.

2026-10-23: game API keys and player feedback

The first version of the developer API.

  • Game API keys: owners and a game's crew create, rotate and revoke one key per studio game on its Developer tab. A key is bk_live_ and 43 characters, shown once and stored as a SHA-256 hash. Every change is in the audit log, and a game that leaves the studio's catalog takes its key with it. See Getting a game's API key.

  • POST /developer/v1/feedback: a game's servers send player feedback with the key, stored once per idempotency key and answered 202 with a receipt. A key pasted into the text is removed before it is stored. See POST /developer/v1/feedback.

  • The Feedback tab: the crew reads and triages the feedback in the panel. See A game's Feedback tab.

  • BlockoutFeedback: a standalone Luau module for games not built on the Template, removed on 2026-10-27 in favour of the Template's platform service.

  • Limits: 120 requests a minute per key and 1,200 for every key together, with 429 and Retry-After over either.

Updated