> 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/june-2025/new-filtering-option-and-supplier-identifier-in-operator-game-list-api.md).

# New Filtering Option & Supplier Identifier in Operator game/list API

Update to Operator Games API – Enhanced Filtering and Supplier Mapping Support

**Effective from:  June 9, 2025**

We’ve added new functionality to the [`POST /operator/generic/v2/game/list`](https://docs.hub88.io/developer-docs/operator-api-reference/games-api.md#get-the-game-list) endpoint to improve data mapping and filtering for Operators.

**What’s new?**

**🎯 Filter by Product**\
You can now include the optional query parameter `product_code` to retrieve only the games associated with a specific product. If no filter is applied, the endpoint will return the full game list as before.

**🔗 Supplier Identifier in Game Response**\
Each game entry now includes a new `supplier_identifier` object that exposes key identifiers from the game supplier, helping you map and compare games more easily with your internal records.

```json
"supplier_identifier": {
  "game_id": "007",    // Supplier’s game ID
  "game_code": "007007007", // Supplier’s desktop game code
  "game_code_mobile": "0071"     // Supplier’s mobile game code (if available)
}
```

This update provides:

* Better control when retrieving games by specific product codes.
* Enhanced data mapping for better synchronization with your internal game lists.
* Improved API transparency for supplier-level identifiers.


---

# 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/june-2025/new-filtering-option-and-supplier-identifier-in-operator-game-list-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.
