March 2024
-added hidemenu parameter to hide game side/top menu. See “hidemenu” inside the C1 chapter.
May 2024
-added exit_url when opening a game to redirect the player to a custom URL when the user will exit the game. See exit_url inside the Game Launch documentation
June 2024
-added multiple RTP versions to launch the game with a specific RTP. Only works for slot games. See paytable_version inside the Game Launch documentation
June 2025
-changed response status required to be -1 (instead of 0 – still works with 0) on rejecting a transaction in balance_adj
-when using cronjob to receive cancelled bets and cancelled wins, the RGS will now send type=cancelbet and type=cancelwin . These transactions will repeat every 5 minutes until they are resolved by the Operator
-added internal_session_id parameter to be sent to the OPERATOR on each balance_adj
July 2025
-changed the required steps to launch new game sessions by generating a game play token. Old method is still functional if preferred, but new method has better security;
-made autoreg=1 default (cannot be changed) when launching games
-released API VERSION 2.0 which focuses on exchanging data in JSON format between all Operator Server < - > RGS Server interactions - see Migrate to 2.0 article if you are using version 1.0
-added optional rg parameter on game launch to control responsible gaming refresh time
-added mandatory txid parameter required to be sent by your server, in the response of balance_adj representing an unique transactionID from your system
-added optional lang parameter to set game language. Refer to the end of the Generate Game Play Token page to see the available languages.
February 2026
-Fixed HMAC signature validation examples (removed JSON_NUMERIC_CHECK to prevent float precision issues)
-Added code samples for Node.js, Python, Java, C#, Go, and Ruby for interacting with our API
-Clarified that 'amount' field is sent as a string (e.g., "-0.2000") in balance_adj endpoint
-Clarified that 'login' field will have a suffix with the _ + CURRENCY
June 2026
Changed: the HMAC signature on balance_adj and getbalance now covers three additional fields — gameid, gpid, currency — appended after amount. This is mandatory for all operators. Requests signed the old way will be rejected .
Action required (all operators): update your signature reconstruction to append gameid, gpid, currency (exact order below):
getbalance: [command, timestamp, login, internal_session_id, uniqid, type, userid, custom_data, currency]
balance_adj: [command, timestamp, login, internal_session_id, uniqid, type, userid, custom_data, amount, gameid, gpid, currency]
Complete integration page with new variables is displayed here.
Seamless-wallet response handling clarified: balance_adj responses are now classified as: status 1 = accepted; status 0 or -1 = rejected (resolved, never retried); any other value, no response, or an unparseable response = undelivered, retried until a definitive answer. Undelivered transactions use an exponential backoff (5, 10, 30, 60, 120, 300, 600 minutes) and are never abandoned. A win that cannot be confirmed in real time no longer blocks the player.
July 2026
Changed (behaviour): on slot games, the force_min_bet / force_max_bet parameters of getGameUrl now describe the TOTAL bet per spin (total = bet per line × paylines) instead of a per-line value. The RGS converts the total to the per-line coin window internally (divided by the game's paylines). EG: force_max_bet=100000 on a 20-payline slot now shows coin sizes up to 5000.00. Table games are unchanged (the values already capped the total bet). If you were sending per-line values for slot games, multiply them by the game's paylines. See the Game Launch documentation.
-force_minchip / force_maxchip now also work on slot games: they narrow the selectable coin sizes (bet per line) directly. On slot games they are ignored when force_min_bet or force_max_bet is also sent (the bet-range parameters take precedence).