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 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.

"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.

Last updated

Was this helpful?