# New parameter and functionality in Operator API transactions endpoint

**Effective from: 19 May 2025**

***

The [`POST /operator/generic/v2/transactions/list` endpoint](https://app.gitbook.com/s/F8iFPgdqAwxIxP5oQMvU/operator-api-reference/transactions-api#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://app.gitbook.com/s/F8iFPgdqAwxIxP5oQMvU/operator-api-reference/transactions-api#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**:

*  [`POST /transaction/bet`](https://app.gitbook.com/s/F8iFPgdqAwxIxP5oQMvU/operator-api-reference/wallet-api#post-transaction-bet) 
*  [`POST /transaction/win`](https://app.gitbook.com/s/F8iFPgdqAwxIxP5oQMvU/operator-api-reference/wallet-api#post-transaction-win) 
*  [`POST /transaction/rollback`](https://app.gitbook.com/s/F8iFPgdqAwxIxP5oQMvU/operator-api-reference/wallet-api#post-transaction-rollback) 

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