console_id values to pass when filtering game or demand queries by platform. You must have the consoles.read scope on your API key to call these endpoints.
Scope required
consoles.read
The console object
Every console endpoint returns records in the following shape:GET /api/v1/consoles
Returns a paginated list of all supported consoles, ordered alphabetically by name. Use this endpoint to populate a platform picker or to build a local ID-to-name mapping.Query parameters
int
Number of results per page. Defaults to
25. Capped by your plan’s max_page_size — confirm the effective value by reading meta.pagination.per_page in the response rather than assuming your requested limit was honored.int
Page number for page-mode pagination. Defaults to
1.string
Opaque cursor token for cursor-mode pagination. Pass the value from
meta.pagination.next_cursor returned in the previous response.string
Pagination mode. Defaults to
page. Set to cursor for more efficient traversal of large result sets.Request
Response 200
GET /api/v1/consoles/{id}
Retrieves a single console by its numeric ID. This is the fastest way to resolve a console name from an ID you already have — for example, to display a platform label alongside a game record.Path parameters
int
required
The numeric ID of the console to retrieve.
Request
Response 200
Error responses
Using console IDs
Console IDs are the connective tissue between the Consoles API and the rest of the 8bitedge platform. You’ll encounter them in two places:- Games API — as the
console_idpath parameter inGET /api/v1/games/console/{console_id}to retrieve all games for a platform. - Demand API — as the
?console_id=query parameter on demand endpoints such asGET /api/v1/demand-intent/gamesto narrow the leaderboard to a single platform.
19 for Nintendo SNES in this example.
Step 3. Pass that ID as a filter to the demand leaderboard.