> 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/may-2025/new-parameter-and-functionality-in-operator-api-transactions-endpoint.md).

# New parameter and functionality in Operator API transactions endpoint

**Effective from: 19 May 2025**

***

The [`POST /operator/generic/v2/transactions/list` endpoint](https://docs.hub88.io/developer-docs/operator-api-reference/transactions-api.md#post-operator-generic-v2-transactions-list) now supports two distinct use cases for retrieving gameplay transactions:

* By time range – using `start_time` and `end_time`
* By round – using the `round` parameter

This update introduces greater flexibility when querying transaction history, making it easier to inspect activity across a period or within a single game round.

#### What is changing?

We’ve added new functionality and stricter validation to the [Get user's gameplay transactions ](https://docs.hub88.io/developer-docs/operator-api-reference/transactions-api.md#get-users-gameplay-transactions)endpoint:

* **New optional parameter**
  * `round` – fetches transactions linked to a specific round ID.
* You **must** specify either:
  * `start_time` and `end_time`, or
  * `round`
  * **If neither a time range nor a round ID is provided, the request will fail with a validation error.**

You can get the **`round`** value is a part of the request call Hub88 makes whenever **Hub88 calls the following Wallet API endpoints**:

* &#x20;[`POST /transaction/bet`](https://docs.hub88.io/developer-docs/operator-api-reference/wallet-api.md#post-transaction-bet)&#x20;
* &#x20;[`POST /transaction/win`](https://docs.hub88.io/developer-docs/operator-api-reference/wallet-api.md#post-transaction-win)&#x20;
* &#x20;[`POST /transaction/rollback`](https://docs.hub88.io/developer-docs/operator-api-reference/wallet-api.md#post-transaction-rollback)&#x20;

#### Why is it changing?

This update provides needed flexible and reliable ways to trace gameplay data — whether over time or within a single round, improving transaction visibility and enforcing clear usage rules to prevent ambiguous or incomplete requests.


---

# 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/may-2025/new-parameter-and-functionality-in-operator-api-transactions-endpoint.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.
