Changelog

All notable changes to this documentation and to the Operator API and wallet callback specifications are recorded here, newest first.

Versioning

The documentation is versioned as MAJOR.MINOR.PATCH. The current version is shown in the top navigation, and previous versions remain available from the same menu.

Part	Raised when	Do you need to change your integration?
MAJOR	A change that is not backward compatible (a field or endpoint is removed or changes meaning). A breaking change ships as a new API path version (e.g. /operator/v2) with an overlap period.	Yes — follow the migration notes
MINOR	Something is added: a new endpoint, request option, response field, error code, game or callback reason value	No, unless you want to use the new feature. Ignore unknown response fields and values
PATCH	Documentation fixes and clarifications with no change in behaviour	No

• The documentation version is separate from the API path version (v1 in /operator/v1).
• Items added after the first release are marked with a badge such as 1.1.0+ where they are described.
• Changes that need action on your side (go-live addresses, new required fields, deprecations) are also announced to your integration contact in advance.

1.0.0 — 2026-10-20

First published version.

• Getting started: overview, onboarding and environments, authentication and signing (with test vectors), conventions, game launch flow.
• Seamless wallet callbacks: balance, debit, credit, rollback — idempotency, timeouts and retries.
• Operator API: game launch, games/lobby/currencies, tables, players, rounds/transactions/reports, operator settings and prepaid credit, dealers, private tables, audit log, error codes.
• Appendix: game codes, integration checklist.
• Environment addresses are written as the placeholders {API_BASE}, {API_HOST} and {GAME_ORIGIN}; the actual addresses are issued per environment during onboarding.