Data
Fields
Every field a game carries on the wire, its type, and where the number comes from.
A game
| Field | Type | Meaning |
|---|---|---|
universeId | integer | The Roblox universe id. The id this API keys on. |
placeId | integer | The start place, where the play link goes. |
name | string | The game's name as Roblox lists it. |
genre | string | The studio's own one-line label, not Roblox's genre field. |
playing | integer | Players online across every server, Roblox's count. |
visits | integer | Lifetime visits, Roblox's count. |
favorites | integer | Favorites, Roblox's count. |
upVotes | integer | Thumbs up, Roblox's count. |
downVotes | integer | Thumbs down, Roblox's count. |
playUrl | string | The game's page on roblox.com. |
Numbers are plain integers, never strings, and never null: a game that Roblox cannot count would not be listed. The site's own fields (art, copy, the studio's descriptions) stay off the API. Field names are camelCase everywhere, on the keyed tier too.
The live read
GET /v1/live carries the studio totals plus a games array whose entries hold universeId, playing, visits, favorites, upVotes and downVotes; the names and links are on GET /v1/games.
Lists
A list that can grow answers { "data": [...], "hasMore": true } and takes ?limit= (50 by default, 200 at most) and ?startingAfter=<id> to page. The keyless lists are fixed and small, so they keep a named key: games and limits.