Skip to content

Basics

API V2 can be used by 3rd party game engines interfacing directly with the hizi.io RGS or for a RGS to RGS integration. It also supplies a call to use the hizi.io certified RNG.

Interfacing to API V2 can be done in either of two ways

  1. Subscribing to the hizi.io RabbitMQ message broker for receiving messages and sending messages via RPC calls sent to the hizi.io message broker. hizi.io provides a set of NPM modules to facilitate communication via the message broker. For other programming languages have a look at https://www.rabbitmq.com/tutorials/tutorial-six-python.html.
  2. Listening to a HTTP port to receive incoming calls and using HTTP POST calls to send data to the hizi.io RGS

Usage of the message broker is recommended by hizi.io as it uses less system resources and has advantages for scalability and failure tolerance. Variant 2 (HTTP/2) has to be used in case of a RGS to RGS integration when the 3rd party RGS is not hosted via hizi.io

Important notes

    All amounts in calls / payload / responses are always in minor units (1/100 of the currency)
    All calls should be idempotent on the hashes passed

Information flow for game engines

game-studio-api figure 3

Information flow for RGS to RGS communication

game-studio-api figure 4