How can we help you?

Search for any helpful articles from our team to find an answer to your question.

Integration documentation for the CasinoWebScripts RGS games API: what we need before you start, the mandatory endpoints, the seamless-wallet calls your platform receives, the optional endpoints, error codes, supported currencies and how to test and finalize your integration.

๐Ÿ‘‹

Introduction

What you need before you start and the order of an integration: the requirements we ask for, how your trial access is enabled and the steps in which the endpoints are wired and tested.

2 articles

๐ŸŒ

Main Endpoints - Mandatory

The calls every integration must implement: passing data to the RGS-CWS API endpoints, listing the available games, generating a game play token and launching a game.

4 articles

๐Ÿ’ฌ

Receiving Data from our API

How the RGS-CWS API talks to your seamless wallet: the balance and bet/win requests your platform receives, how to trust the data we send, what happens when your wallet refuses a win (win_rejected) and how timeouts are handled.

4 articles

๐Ÿ›Ÿ

Advanced Endpoints - Optional

Optional endpoints beyond the mandatory ones: server time, game round history, logging a user out, last activity, total bets and wins, timed-out bets and wins and their resolution, free rounds and feature spins (grant, cancel, status), prize drops and data for incomplete gameplays.

13 articles

๐Ÿ—‚๏ธ

Other Information

Everything around the integration itself: migrating from API 1.0 to 2.0, the FAQ, the error codes, the update history (changelog), the supported currencies and how to test and finalize your integration.

6 articles