> For the complete documentation index, see [llms.txt](https://docs.hub88.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hub88.io/api-changelog/november-2026/access-multiple-thumbnail-sizes-and-game-assets-in-operator-games-api.md).

# Access Multiple Thumbnail Sizes and Game Assets in Operator Games API

**Effective from: 12 November 2026**

***

The [`POST /operator/generic/v2/game/list`](https://docs.hub88.io/developer-docs/operator-api-reference/games-api.md#post-operator-generic-v2-game-list) response now includes an `assets` object for every game. It returns all available thumbnail sizes, the background and a raw materials folder, each under a fixed key. Until now, the API only returned the 4:3 thumbnail and the background.

{% hint style="info" %}
This applies to the **Operator Generic API**. The change is backwards compatible: `url_thumb` and `url_background` are unchanged.
{% endhint %}

### What's new?

#### The `assets` object

Each game in the response now carries an `assets` object with three groups:

1. `backgrounds`: `default`, the game background image
2. `raw_materials`: `folder`, a link to the game's source asset files (not an image)
3. `thumbnails`: `4_3` (Thumbnail 4:3, horizontal, default), `3_4` (Thumbnail 3:4, vertical) and `1_1` (Thumbnail 1:1, square)

```json
"assets": {
  "backgrounds": {
    "default": "https://cdn.hub88.io/onetouch/backgrounds/ont_blackjackclassic.jpg"
  },
  "raw_materials": {
    "folder": "https://cdn.hub88.io/onetouch/folder/"
  },
  "thumbnails": {
    "1_1": "https://cdn.hub88.io/onetouch/ont_blackjackclassic_1_1.png",
    "3_4": "https://cdn.hub88.io/onetouch/ont_blackjackclassic_3_4.jpg",
    "4_3": "https://cdn.hub88.io/onetouch/ont_blackjackclassic.jpg"
  }
}
```

**How it works**

* All three groups are always present. A group can be an empty object (`{}`).
* A format key appears only when that asset exists for the game. You’ll never receive `null` or an empty string inside `assets`.
* `assets.thumbnails.4_3` is returned only when the game has a `url_thumb`, and it has the same value. If `url_thumb` is `null` or an empty string, `4_3` is left out. The same applies to `assets.backgrounds.default` and `url_background`.
* Other formats don’t depend on `url_thumb`. A game can have a 3:4 thumbnail but no 4:3 thumbnail:

```json
"assets": {
  "backgrounds": {},
  "raw_materials": {},
  "thumbnails": {}
}
```

* Use each URL exactly as returned. File extensions vary between games, so don't build URLs from the game code or a file suffix.
* `assets.thumbnails.4_3` has the same value as `url_thumb`, and `assets.backgrounds.default` has the same value as `url_background`.
* We'll add new formats over time as new keys. Make sure your integration ignores keys it doesn't recognise, as described in our [forward compatibility notice](https://docs.hub88.io/api-changelog/october-2026/operator-api-your-integration-must-ensure-forward-compatibility.md).

Extra sizes are already available for the existing catalogue, and new games get them as they're released.

### This update provides

* **The right image for every layout.** Use vertical 3:4 tiles in mobile lobbies and square 1:1 images in grids, without resizing or cropping the 4:3 thumbnail.
* **No more guessing URLs.** Stop editing file names by hand or downloading full asset packs. Every available size comes straight from the API.
* **Room to grow.** New formats appear as new keys, with no change to your request.
* **Full backwards compatibility.** `url_thumb` and `url_background` work exactly as before. No action is needed unless you want the new sizes.

If you have any questions or need support updating your integration, please contact your Hub88 account manager or our technical support team.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hub88.io/api-changelog/november-2026/access-multiple-thumbnail-sizes-and-game-assets-in-operator-games-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
