Overview
HTML5 clients run in the browser. The current product includes web pages, mobile adaptation and a Telegram shell. Games use server configurations, sessions and round history.
Embedding
Game clients support iframe embedding. Domain policies, permissions, screen sizes and return behavior must be agreed for each platform.
Sessions and access
Money actions in the current system are bound to authenticated sessions. Preparation, launch and subsequent actions are checked by the server. The external authorization model is defined by the integration contract.
Rounds and results
The server controls rules and results. The current architecture includes history, versioned rules and idempotent retries. Availability of a visual replay depends on the game.
Screens and devices
Validation should cover desktop, mobile browsers and Telegram: game viewport, fullscreen behavior, gestures, orientation, sound and recovery after connectivity loss.
Connection plan
Before connecting, the game list, environment, authorization, data, limits and acceptance criteria are agreed. Validation then takes place in a separate environment.
Presentations and demos
Ganja Gold, Vape Zone, Sweet Kingdom and DARK DESIRE have separate demos with a test balance and no real money. Demonstrations of other games are arranged with the team. A demo is not an external integration API.
What this document does not promise
This overview is a starting point for integration. Access, the technical contract and connection terms are agreed with the studio team.