# Operator Games API: 'country' field validation

**Announced:** 1 June 2026 

**Effective** **from**: 15 June 2026

***

{% hint style="warning" %}
**Action is required to maintain your integration.** 

From **15 June 2026**, Hub88 will **enforce** ISO 3166-1 validation on the `country` field in the Operator Games API. 

Requests with invalid country values will be rejected with a `400 Bad Request` response. 

**Please review your integration before this date.**
{% endhint %}

### **What's changing?**

The `country` parameter on [`POST /operator/generic/v2/game/url`](/developer-docs/operator-api-reference/games-api.md#post-operator-generic-v2-game-url) will be strictly validated against the **ISO 3166-1 alpha-2 standard**.

Valid values are two-letter uppercase country codes, for example `EE`, `US`, `NG`, or `GB`.

From **15 June 2026**, requests containing non-conforming values will return a `400 Bad Request` error. This includes:

* Lowercase codes (e.g. `ng` instead of `NG`)
* Invalid strings (e.g. `-`, `892346979034093-`)
* Any value not in the ISO 3166-1 alpha-2 standard

Example of a valid request:

```json
{
  "user": "player123",
  "token": "your-token",
  "operator_id": 10,
  "game_code": "example_game",
  "currency": "EUR",
  "country": "EE"
}
```

**Examples accepted values:** 

<details>

<summary><strong>Click to expand</strong></summary>

```json
[
        "XX",
        "AD",
        "AE",
        "AF",
        "AG",
        "AI",
        "AL",
        "AM",
        "AO",
        "AQ",
        "AR",
        "AS",
        "AT",
        "AU",
        "AW",
        "AX",
        "AZ",
        "BA",
        "BB",
        "BD",
        "BE",
        "BF",
        "BG",
        "BH",
        "BI",
        "BJ",
        "BL",
        "BM",
        "BN",
        "BO",
        "BQ",
        "BR",
        "BS",
        "BT",
        "BV",
        "BW",
        "BY",
        "BZ",
        "CA",
        "CC",
        "CD",
        "CF",
        "CG",
        "CH",
        "CI",
        "CK",
        "CL",
        "CM",
        "CN",
        "CO",
        "CR",
        "CU",
        "CV",
        "CW",
        "CX",
        "CY",
        "CZ",
        "DE",
        "DJ",
        "DK",
        "DM",
        "DO",
        "DZ",
        "EC",
        "EE",
        "EG",
        "EH",
        "ER",
        "ES",
        "ET",
        "FI",
        "FJ",
        "FK",
        "FM",
        "FO",
        "FR",
        "GA",
        "GB",
        "GD",
        "GE",
        "GF",
        "GG",
        "GH",
        "GI",
        "GL",
        "GM",
        "GN",
        "GP",
        "GQ",
        "GR",
        "GS",
        "GT",
        "GU",
        "GW",
        "GY",
        "HK",
        "HM",
        "HN",
        "HR",
        "HT",
        "HU",
        "ID",
        "IE",
        "IL",
        "IM",
        "IN",
        "IO",
        "IQ",
        "IR",
        "IS",
        "IT",
        "JE",
        "JM",
        "JO",
        "JP",
        "KE",
        "KG",
        "KH",
        "KI",
        "KM",
        "KN",
        "KP",
        "KR",
        "KW",
        "KY",
        "KZ",
        "LA",
        "LB",
        "LC",
        "LI",
        "LK",
        "LR",
        "LS",
        "LT",
        "LU",
        "LV",
        "LY",
        "MA",
        "MC",
        "MD",
        "ME",
        "MF",
        "MG",
        "MH",
        "MK",
        "ML",
        "MM",
        "MN",
        "MO",
        "MP",
        "MQ",
        "MR",
        "MS",
        "MT",
        "MU",
        "MV",
        "MW",
        "MX",
        "MY",
        "MZ",
        "NA",
        "NC",
        "NE",
        "NF",
        "NG",
        "NI",
        "NL",
        "NO",
        "NP",
        "NR",
        "NU",
        "NZ",
        "OM",
        "PA",
        "PE",
        "PF",
        "PG",
        "PH",
        "PK",
        "PL",
        "PM",
        "PN",
        "PR",
        "PS",
        "PT",
        "PW",
        "PY",
        "QA",
        "RE",
        "RO",
        "RS",
        "RU",
        "RW",
        "SA",
        "SB",
        "SC",
        "SD",
        "SE",
        "SG",
        "SH",
        "SI",
        "SJ",
        "SK",
        "SL",
        "SM",
        "SN",
        "SO",
        "SR",
        "SS",
        "ST",
        "SV",
        "SX",
        "SY",
        "SZ",
        "TC",
        "TD",
        "TF",
        "TG",
        "TH",
        "TJ",
        "TK",
        "TL",
        "TM",
        "TN",
        "TO",
        "TR",
        "TT",
        "TV",
        "TW",
        "TZ",
        "UA",
        "UG",
        "UM",
        "US",
        "UY",
        "UZ",
        "VA",
        "VC",
        "VE",
        "VG",
        "VI",
        "VN",
        "VU",
        "WF",
        "WS",
        "YE",
        "YT",
        "ZA",
        "ZM",
        "ZW"
]
```

</details>

### **Why is it changing?**

The `country` field is used across session creation, supplier requests, reporting, and compliance logic. Invalid values can propagate incorrect geo-data to game suppliers and affect regulatory reporting. This validation ensures data integrity across the platform.

### **Impact**

Operators sending non-standard `country` values will receive a `400 Bad Request` response from 15 June 2026. Affected game launch requests will fail until the integration is updated.

{% hint style="warning" %}
⚠️ **Action required by 15 June 2026**

You **must review your integration** and ensure all requests to `POST /operator/generic/v2/game/url` send a valid, uppercase ISO 3166-1 alpha-2 country code in the `country` field. Failure to update before this date will result in failed game launch requests.

For the full list of valid country codes, refer to the [ISO 3166-1 alpha-2 standard](https://www.iso.org/iso-3166-country-codes.html).

If you need support updating your integration, please contact your Hub88 account manager or our technical support team.
{% endhint %}


---

# 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/june-2026/operator-games-api-country-field-validation.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.