For the complete documentation index, see llms.txt. This page is also available as Markdown.

Operator Games API: 'country' field validation

Announced: 1 June 2026

Effective from: 15 June 2026


What's changing?

The country parameter on 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:

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

Examples accepted values:

Click to expand

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.

Last updated

Was this helpful?