Stores one piece of player feedback for the game the key belongs to. The game's crew reads it on the game's Feedback tab in the panel, newest first, and moves it through New, Seen, Planned, Done and Ignored; the assistant can summarise it.
Request to POST /developer/v1/feedback
POST/developer/v1/feedback
Headers
AuthorizationstringRequiredBearer bk_live_<the game's key>.Content-TypestringRequiredapplication/json. Any other body type is refused with415.
POST https://studio.blockoutgames.com/developer/v1/feedbackAuthorization: Bearer bk_live_<the game's key>Content-Type: application/json{ "idempotencyKey": "3f1c9a0e-1b2d-4c5e-8f90-123456789abc", "category": "bug", "text": "The shop button does nothing", "playerId": 1234567890, "placeId": 98765, "serverVersion": "412"}A test from curl is stored like any other feedback and shows on the game's Feedback tab; mark it Ignored there. Retries and a full sender: Sending feedback over HTTP.
The feedback body fields
Body
idempotencyKeystringRequired- 8 to 64 letters, digits,
-or_, such as a GUID. A new one for each piece of feedback, and the same one for every retry of it; unique per game. categorystringRequiredbug,suggestion,balance,praiseorother.textstringRequired- 1 to 2,000 characters after trimming. A game key pasted into it is replaced with
bk_live_[removed]before it is stored. playerIdnumber | null- The player's Roblox
UserId. Null or left out for feedback from no one player. placeIdnumberRequired- The place the server runs,
game.PlaceId. serverVersionstring | null- 1 to 64 characters after trimming, such as
tostring(game.PlaceVersion). Null or left out when unknown.
Any other field is refused. The body may be at most 16 KiB.
What POST /developer/v1/feedback answers on success: the receipt
202 with the receipt:
{ "id": "6f0c1e7a-3b52-4f7d-9a1e-0d2c5b8e4a11", "receivedAt": "2026-10-24T10:02:31.000Z" }FeedbackReceipt
idstring- The stored feedback's id, a UUID. The same for every retry with the same idempotency key.
receivedAtstring- When the platform first stored it, ISO 8601 UTC.
Retrying feedback with the same idempotency key
The platform stores feedback once per idempotency key and game. A retry with the same key answers the first receipt and stores nothing, even if its text differs, so a retry after a timeout never makes a duplicate. Retry a 429 or a 5xx with the same body; never retry a 400, 401 or 413 unchanged. More on Sending feedback over HTTP.
How feedback counts against the limits
Feedback shares the key's 120 requests a minute with the reads, and the 1,200 for every key together. The per-address write limit (240 a minute from one address) applies before the key is read. Feedback is never cached, and posting it never empties the cached market answers.
Errors from POST /developer/v1/feedback
| Status | error.code | When and what to do |
|---|---|---|
| 400 | validation_failed | A field is missing or breaks its rule, or an unknown field was sent; error.issues names each. Fix the body |
| 401 | unauthenticated | The key is missing, malformed, wrong or revoked, or its game left the catalog. Check the secret |
| 413 | payload_too_large | The body is over 16 KiB. Send less |
| 415 | unsupported_media_type | The body is not sent as application/json |
| 429 | rate_limited | Over a limit. Wait the Retry-After seconds, then retry with the same body |
| 503 | unavailable, timeout | The platform is busy. Retry with backoff and the same body |
Bodies: Errors, limits and polling.
Updated