Game Catalogue
Find launch identifiers and capability flags with the currency-filtered getGameList command.
/v1/commandsgetGameListOmit idempotency keyOn this page
Request#
Call getGameList with scope proxy:getGameList or proxy:*. Omit Idempotency-Key.
{
"method": "getGameList",
"currency": "USD",
"list_type": 2
}| Field | Required | Accepted value |
|---|---|---|
currency | Yes | Three-letter uppercase code enabled for your workspace |
list_type | No | 1 or 2; default 1 |
show_additional | No | Boolean; default true |
show_systems | No | 0 or 1; default 0 |
The current connection returns compact records regardless of these legacy presentation options. It filters inventory by provider currency coverage; the gateway also applies workspace game entitlements.
Response#
{
"error": 0,
"response": [
{
"n": "Example game",
"p": "Example provider",
"s": "12/737",
"fs": false,
"fb": false,
"d": false,
"id": 737
}
]
}The example is illustrative. In compact records, n is the game name, p the provider, s the launch ID, fs the free-round flag, fb the feature-buy flag, and d the demo flag. The current connection sets fb and d to false; do not treat them as a complete capability inventory. Demo availability is confirmed by a successful demo request.
The compatibility contract can also return a map of records or detailed records. In detailed records, the launch identifier is id_hash. Preserve identifiers exactly; never substitute the numeric id field.
Use the catalogue#
Use a returned <brand_id>/<game_uid> identifier to launch a game or grant free rounds. Your currency entitlement and provider availability still apply at launch. Cache catalogue metadata as appropriate, refresh it regularly, and handle removed or unavailable games.