> 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/july-2025/removal-of-the-ip-field-from-operator-and-supplier-api.md).

# Removal of the "ip" Field from Operator and Supplier API

**Effective from:** 14 August 2025

***

### What’s changing?

We are removing the `ip` field from the request payload of the following API endpoints:

* [`POST /operator/generic/v2/game/url`](https://docs.hub88.io/developer-docs/operator-api-reference/games-api.md#get-a-game-url) (**Operator** **API**)
* [`POST /game/url`](https://docs.hub88.io/developer-docs/supplier-api-reference/games-api.md#get-a-game-url) (**Supplier** **API**)

From 14 August 2025, this field will no longer processed in API requests.

### Why is it changing?

As part of our efforts to ensure compliance with evolving regulatory standards and to uphold best practices in data privacy, we are removing this field from both our APIs and associated documentation.

### Impact

* We **strongly recommend** that all operators and suppliers **remove the `ip` parameter** from their requests to reflect the current specification and avoid transmitting unnecessary data.
* This change is **backwards compatible**: any requests still containing the `ip` field will not cause errors, but the value will be ignored or altered to `0.0.0.0` by our systems.
* No other fields or behaviours within these endpoints are affected.

If you have any questions about this change or need support updating your integration, please reach out to your Hub88 account manager or the technical support team.


---

# 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/july-2025/removal-of-the-ip-field-from-operator-and-supplier-api.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.
