API requests flow

Following would be the typical flow of few of the API requests from operator to RGS NG-Connect API.

• CasinoSite (frontend of the operator) is the example website name.
• Player A visits and logins into CasinoSite by providing username and password
• CasinoSite verifies username and password match and performs typical checks. If everything is fine, a unique session ID (token) is created for the player in CasinoSite platform.
• Player A visits the game lobby.
• CasinoSite makes the API call GetGames() to NG-Connect to get the list of games enabled for the CasinoSite. NG-Connect replies with the list of games enabled.
• List of games are shown to the player in game lobby.
• Player A clicks on any of NG games. CasinoSite needs to make GameLaunch() API call to NG-Connect API by providing the required details as part of API request.
• NG-Connect registers the session ID and creates player details if not present and ignores if already available in RGS platform and returns game launch URL to CasinoSite.
• Game is launched (in a new window or redirected to the URL) in CasinoSitewith the given GameLaunch URL sent by NG-Connect.
• Player A plays the game which results in debits and credits. RGS game engine makes debit and credit calls to NG-Connect accordingly.
• The API NG-Connect, realizing that the player’s wallet is hosted in CasinoSite platform, redirects the calls to the CasinoSite API platform. CasinoSites designs and implements this API and performs the operations on their account wallets. In return, CasionSite sends player’s balance details post debit / credit.
• During every call, API_KEY is passed to NG-Connect by CasinoSite API.
• During all these calls, the session ID is passed to NG-Connect by CasinoSite and same session ID will be sent back to CasinoSite during player transactions API calls. CasinoSite recognizes the provided session ID and performs the operations on their wallet.

GetGames()

GameLaunch()

Wallet Typical Flow

Debit() & Credit() Flow