Current Integration/Beta

Overview

This section explains all the new features that are made available in the INTEGRATION environment. This environment is updated at least weekly with new features and after each update, this section will contain a complete list of all new features, bug fixes and changes (from the Latest Stable Release).

BREAKING CHANGES

No breaking changes

New Features

ThrillPots

  • Exclusion Rules for contributions and jackpot visibility
    • Exclusion rules make it possible to restrict access to jackpots based on:
      • Game Code(s) -- you can now prevent certain game codes from participating in the jackpot
      • Player ID(s) -- you can now prevent certain players from participating in the jackpot
      • Vertical ID(s) -- you can prevent certain verticals from participating in the jackpot (eg "sports")
    • The "Get Jackpot For Source" APIs now support an additional query parameter (game_code) which can be passed as context for exclusion rule checks. This will allow you to determine whether a jackpot should be shown to a player in the context of a specific game or not.

ThrillConnect

  • Added APIs to provide Latest Winners functionality to frontend clients

ThrillOffice

  • Jackpot Template Management: The new Jackpot Template Management view provides complete functional control over your Jackpot Templates, including: - The ability to instantiate new Jackpot Instances from a template - The ability to switch an existing instance to a new template (model switching)

  • The Reconciliation Report has been improved and provides:

    • a grouped view for all instances (per month)
    • a delta view for monthly movement (per instance or per group)

Changes/Improvements

ThrillPots

  • Improvements to Community Payout Strategy: Random Active Players

    • Improvements have been made to the random selection mechanism for players that fall under the Active Players Payout Strategy.

  • Always Fair Multicurrency minimum bet constraints are now configurable for Percentage Based Jackpots.

Bug Fixes

ThrillGate

  • If the operator platform exchanges the token passed in SWAuthRequest with another token to be used, the new token is now honoured and used.