# Enhancements to Freebet Campaign Management and Rewards Retrieval

**Released:** 13 August 2025

***

We’ve made several improvements to the **Operator API** to provide greater visibility, control, and flexibility when working with Freebet Campaigns and Rewards.

### 1. New endpoint: Retrieve Campaign Details by UUID

Operators can now fetch the full configuration details of a specific Freebet Campaign by its unique identifier.

**Endpoint:** [`POST /operator/generic/v2/freebet/campaigns/info`](/developer-docs/operator-api-reference/freebets-api.md#get-a-campaign-by-uuid)

**Use case:** Ideal for validating campaigns in real time, enhancing reporting, or enabling detailed customer support queries.

**Request body:**

```json
{
    "campaign_uuid": "007-jb07-jb07-jb007-007007007",
    "operator_id": 7
}
```

For the request, both `campaign_uuid` and `operator_id` are required.

**Response includes:** campaign name, active period, game code, currency, bet value, and number of bets.

***

### 2. Additional filtering for Campaign List endpoint

The existing [**Get Campaigns List**](/developer-docs/operator-api-reference/freebets-api.md#get-a-list-of-campaigns) endpoint now supports additional optional filters for more precise results.

**Endpoint:** [`POST /operator/generic/v2/freebet/campaigns/list`](/developer-docs/operator-api-reference/freebets-api.md#get-a-list-of-campaigns)

**New filters:**

* `start_time` — return Campaigns starting on/after this time,
* `end_time` — return Campaigns ending on/before this time,
* `name` - filter Campaigns by name,
* `prepaid_uuid` - filter Campaigns by prepaid\_uuid,
* `operator_reference` - return Campaigns related to the specified operator reference.

***

### 3. Campaign UUID in Freebet Transactions

Two wallet endpoints now include the `campaign_uuid` in the transaction metadata for tracking Freebet-related activity. This addition improves traceability of transactions to specific campaigns.

**Affected endpoints:**

* [`POST /transaction/win`](/developer-docs/operator-api-reference/wallet-api.md#update-users-balance-based-on-transaction-win)
* [`POST /transaction/bet`](/developer-docs/operator-api-reference/wallet-api.md#update-user-balance-based-on-transaction-bet)

**Example:**

```json
...
"meta": {
    "operator_reference": "reward_001",
    "campaign_uuid": "7b5c8a93-4d3a-4bfb-8554-f923d46aa485"
}
...
```

***

### 4. New Endpoint: Get a List of Rewards

Operators can now retrieve a paginated list of Rewards using the new Rewards List endpoint, in order to see all available rewards as well as filter them by Campaign or by time range. 

**Endpoint:** [`POST /operator/generic/v2/freebet/rewards/list`](/developer-docs/operator-api-reference/freebets-api.md#get-a-list-of-rewards)

**Request body:**

```json
{
  "operator_id": 7,
  "campaign_uuid": "7b5c8a93-4d3a-4bfb-8554-f923d46aa485",
  "start_time": "2017-11-05T13:15:30",
  "end_time": "2017-11-05T13:15:30",
  "user": "john12345",
  "pagination": {
    "cursor": "eyJpZCI6OTAiMjAyNC0wNS0xMFQxMzozMDoyMVoifQ",
    "limit": "50"
  }
}
```

**Response includes:** an array of rewards matching the requested criteria with all details available per reward  and pagination object.

**Key notes:**

* Pagination is handled via cursors
* At least one of the following is required in request in addition to `operator_id` : `campaign_uuid`, `reward_uuid`, or a time range (`start_time` + `end_time`)

***

If you have any questions or need support updating your integration, please contact your Hub88 account manager or our technical support team.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hub88.io/api-changelog/august-2025/enhancements-to-freebet-campaign-management-and-rewards-retrieval.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.