> 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/december-2025/operator-games-api-sdk-now-supports-onetouch-originals.md).

# Operator Games API SDK  Now Supports OneTouch Originals

**Released:** 18 December 2025

***

We’ve released a new update to the [**Operator Games API SDK**](https://docs.hub88.io/developer-docs/operator-sdks/operator-games-api-sdk.md), expanding supplier support and improving how operators can build richer, more interactive game experiences.

This release focuses on three key improvements: native support for [**OneTouch Originals**,](https://docs.hub88.io/developer-docs/operator-sdks/operator-games-api-sdk/using-onetouch-originals-in-the-sdk.md) new **event listening capabilities**, and clearer guidance for migrating from iframe-based integrations to the SDK.

### What’s new?

### **1. OneTouch Originals support (new supplier)**

You can now load **OneTouch Originals** games directly through the Operator Games API SDK. Games are automatically recognised and configured by the SDK, giving you instant access to original titles without changing your integration model.

<a href="https://docs.hub88.io/developer-docs/operator-sdks/operator-games-api-sdk/using-onetouch-originals-in-the-sdk.md" class="button primary">Read more about OneTouch Originals in the SDK</a>

### **2. Native game event listening**

The SDK now exposes native events for OneTouch Originals games, allowing you to listen for gameplay moments such as:

* Game round started
* Game round ended
* Win / loss outcomes
* Balance updates

This makes it easier to trigger custom UI behaviour such as win animations, balance refreshes, or real-time player feedback directly from your frontend.

Example:

{% code overflow="wrap" lineNumbers="true" %}

```javascript
window.addEventListener('hub88-games-sdk', (e) => {
  const event = e.detail.event
  console.log('Hub88 Event:', event)
})
```

{% endcode %}

<a href="https://docs.hub88.io/developer-docs/operator-sdks/operator-games-api-sdk/using-onetouch-originals-in-the-sdk.md" class="button primary">Read more about OneTouch Originals in the SDK</a>

### **3. New iframe → SDK migration guide**

We’ve added a dedicated migration guide to help operators move from iframe-based integrations to native SDK loading. The guide walks you through removing iframes, switching to the SDK, and validating your setup in a safe, step-by-step flow.

<a href="https://docs.hub88.io/developer-docs/operator-sdks/operator-games-api-sdk/migration-from-iframe-integration.md" class="button primary">Read the migration guide</a>

### 4. Updated SDK version

The **OneTouch Originals** support is available from **SDK version 1.1.2**.

**New CDN:**

```html
<script src="https://cdn.hub88.io/games-sdk/hub88-games-sdk-1.1.2.js"></script>
```


---

# 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/december-2025/operator-games-api-sdk-now-supports-onetouch-originals.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.
