The Developer tab (/studio/<universe id>/developer) holds the game's platform API key, the one key its Roblox servers send with every call to the developer API, and shows how much they have used it. Under them, Connect your game walks through putting the key to work in four steps, and Endpoints lists every route with its page in the API reference. Only the game's crew and owners can manage the key or see its usage.
Who can see the Developer tab
Owners and the game's crew (the developers on its project and its lead) see the key, its usage, and Create key, Rotate key and Revoke key.
The API key card on the Developer tab
The tab leads with the key. Beside its title, a badge says where it stands: Active, Active, never used (no server has sent it yet) or No key. With a key, the card shows:
- Key
bk_live_…and its last four characters. The whole key is never shown again after it was made, to anyone, owners included.- Created
How long ago, and by whom.
- Last used
When a server last sent it, to the minute, or "Never".
- Limit
Requests a minute, for every server of the game together: 120 by default, the same number
GET /developer/v1/keyreports.
Without one, it says "No key yet" and the limit a key would have. A game has at most one key in use.
What a game key is made of
A key is bk_live_ followed by 43 characters (256 random bits from the system's secure random source, in base64url). The platform stores only its SHA-256 hash and its last four characters, so nobody, owners and the database included, can read a key back. On every request the API hashes the key it is sent and looks the hash up; nothing caches the answer, so a rotated or revoked key, or a key whose game left the studio, stops working on its very next request. Why it is built this way: Keeping the key safe.
A game key's life: create, rotate, revoke
A game starts with no key. Create key makes the first one. Rotate key makes a new key and revokes the old one in the same step, so there is never a moment with two keys or none. Revoke key stops the key with nothing in its place; Create key then makes a new one. A revoked key never works again.
How to create a game's API key
Open the Developer tab
Open the game's hub from Studio games, then Developer.
Create the key
Choose Create key.
Copy it now
In Copy the key now, choose Copy key. This is the only time it is shown.
Store it in the experience's secrets
Put it in the experience's Roblox secrets as described in Getting a game's API key.
Tick the checklist, then Done
Tick I copied the key, I stored it as the BlockoutApiKey secret in the Creator Dashboard and Allow HTTP Requests is on. Done works once all three are ticked; copying ticks the first for you.
How to rotate a game's API key
Rotate whenever the key may have been seen by someone who should not have it.
Rotate it
On the Developer tab, choose Rotate key, then confirm.
Copy the new key
Copy the new key from the dialog, which says the old one has stopped working. It is shown once, with the same checklist.
Replace it in the secrets
Put the new key in the experience's Roblox secrets in place of the old one. Until you do, the game's servers are refused (401), because the old key stopped working the moment you rotated.
A rotated key's usage starts from zero.
How to revoke a game's API key
Revoke it
On the Developer tab, choose Revoke key, then confirm.
Remove it from the secrets
Delete the key from the experience's Roblox secrets; it will never work again.
Every create, rotate and revoke is written to the audit log under Games, naming the game but never the key.
What the Developer tab asks the API
The tab uses the panel's own API, with your session. These routes are not part of the developer API a game's servers call, and none of them is cached.
GET/v1/studio/games/:id/api-key
Whether you may manage the key, the key's fingerprint, creator and last use, and its usage. For anyone but owners and the crew it answers with no key and no usage.
POST/v1/studio/games/:id/api-key
Creates the first key. Answers with the key's details and the secret, the only answer that ever holds it. 409 when the game already has a key: rotate it instead.
POST/v1/studio/games/:id/api-key/rotate
Revokes the key in use and issues a new one in one transaction, with the new secret in the answer. 404 when the game has no key.
DELETE/v1/studio/games/:id/api-key
Revokes the key in use; answers 204. 404 when the game has no key.
Create, rotate and revoke answer 403 to anyone but owners and the game's crew, and need the panel's x-requested-with header. An owner may revoke the key of a game even after it left the studio, so no key outlives its game.
Connect your game
Four numbered steps for a game's servers, each ticked once it is done where the page can tell:
- 1. Create the key
Done once the game has a key, naming its fingerprint; otherwise Create key above.
- 2. Keep it in Roblox secrets
The
BlockoutApiKeysecret in the Creator Dashboard, with the API's domain (studio.blockoutgames.com); the same in Studio's Local Secrets to test there, and Allow HTTP Requests. The Template'sPlatformServicereads it withHttpService:GetSecret.- 3. Check the key from a server
platform = truein the Template'sConfig/Features.luau, then a code card with Luau (PlatformService.key()) and cURL (GET /developer/v1/key) tabs.- 4. Send feedback and read the market
The key's limit, shared by every server, and a code card with Luau (
PlatformService.sendFeedbackandPlatformService.games) and cURL (POST /feedback).
Each code card has a copy button for the tab shown. The examples never hold a real key: cURL sends bk_live_…, which you replace by hand, and the Luau reads the key from the secret.
Endpoints
Every route of the developer API, each with its method (GET or POST), its path under https://studio.blockoutgames.com/developer/v1 and what it does: POST /feedback, GET /key, GET /games, GET /games/:id, GET /games/:id/history, GET /genres and GET /market. Each opens its page in the API reference on the docs site, as does API reference at the top of the card. Every call sends Authorization: Bearer bk_live_….
The full guides are in Developers: the feedback API, the Luau module and keeping the key safe.
Key usage on the Developer tab
Under the key, the Usage card counts the requests made with the key in use, per UTC hour, over the last 24 hours and 7 days. Without a key it says "No key in use"; with a key no server has sent yet, "No requests yet"; to anyone off the crew, "For the game's crew". If the counts cannot be read just then, it says "Usage is unavailable" and asks you to reload; the key still works.
Requests, 24 hours
Every request the key made in the current UTC hour and the 23 before it, whatever the answer. Under it: how many were refused or failed (any answer other than a success or a rate limit).
Requests, 7 days
The same over the current UTC hour and the 167 before it, with how many were refused or failed.
Answered, 7 days
The share of the 7 days' requests that were answered (a success, or "not modified"), with how many.
Rate limited, 7 days
How many requests over 7 days were turned away for going over the limit (answered 429), with how many of those were in the last 24 hours. The limit is 120 requests a minute per key, for every server of the game together, and 1,200 a minute for every game's key together (the platform's defaults). A game that is rate limited often should cache answers for a minute and read games in batches; see the feedback API.
By outcome
Two bars, the last 24 hours and the last 7 days, split into Answered, Rate limited and Refused or failed, each with its count and share.
By route, 7 days
A bar for each route, POST /feedback, GET /key, GET /games, GET /games/:id, GET /games/:id/history, GET /genres and GET /market, as long as its requests over 7 days against the busiest, with its count in the last 24 hours under it.
What key usage counts
Counts are kept per key and UTC hour for about eight days, so the 7 days are always complete.
A request with a wrong or revoked key belongs to no key and is not counted.
An answer of "not modified" (304) counts as a success.
Counting never slows or fails a request: if the counter is away, a request is simply not counted.
How fresh the Developer tab is
The key and its usage are read when the page opens; reload to see new requests. Last used is kept to the minute.
The Developer tab on a phone
Every card takes the whole width below 1280 px; from 1280 px Connect your game and Endpoints sit side by side. The key's details stack one per line on a phone, two across from 640 px and four from 1280 px. The usage tiles sit two across on a phone; the outcome bars and the routes sit one above the other below 1024 px. A long line of code scrolls sideways inside its card, never the page.
Related: A studio game's pages, A game's Feedback tab, Getting a game's API key, Errors, limits and polling, POST /developer/v1/feedback.
Updated