Supplier API Overview
Last updated
Was this helpful?
Last updated
Was this helpful?
The Supplier API is designed for game developers and distributors to enable seamless integration with the Hub88 platform. By leveraging this API, gaming content can be effortlessly offered to Hub88's network of partner operators.
Before the integration, the game Supplier generates a private/public key pair and sends the public key to Hub88. Hub88 sends its public key to the game Supplier. The body of all requests will be signed with RSA-SHA256 using the respective private key and encoded to BASE64 (We have code examples in few programming languages). The signature will be placed in the X-Hub88-Signature header. Hub88 and the game Supplier need to verify all Wallet API requests are using the public key provided. The game Supplier verifies all Games API requests using the public key provided by Hub88.
Example:
Request body:{"user":"3nYTOSjdlF6UTz9Ir","country":"XX","currency":"EUR","operator_id":1,"token":"cd6bd8560f3bb8f84325152101adeb45","platform":"GPL_DESKTOP","game_code":"ctl_dragonrising","lang":"en","lobby_url":"https://examplecasino.io","ip":"::ffff:10.0.0.39"}
Private key example for signing the example request here.
Correct signature:
FFdiceKlsnmrBMhWopZYQXrJSMqxJWkynbaiOnuUE1p4mrg2UydlSAdKbOWQZ7o5USbA3SHPum3XuRCa9INWbcp+fdcOhjz0S0JLKF6uXJR2T8zlF+L+8v2lkBzPOvLg6yRuUyspxtcHB6Vlyd0Sj4v8vk5HxoVv1ZV7EpJglzHs7xKchuifjjhUwkX7AAZwvJCNKo/VZrhtfxHd/k8aq7+9h7AztiiiLO7CXbEbo8snDqMqoB/tBAImv45NcAuReBZGb3QY37MbRoOT/uQGj+9ae5VRNpJ74qs3COraDqZ5kqzsa5SjN1cML2foP13Deqp0FTY0Ek521d8CPWQY6A==
Wallet API requests have to be idempotent. All requests contain a request_uuid field. Hub88 will ensure that requests with the same request_uuid are not processed twice while the response will be the same for all duplicate requests, excluding the /supplier/generic/v2/user/balance call.
Once you meet the prerequisites, the process on high-level as follows.
Hub88 will obtain a game URL from the game supplier on behalf of the player and Operator.
Redirect the operator's player to the URL provided by the Game Provider.
Respond to in-game events by forwarding wallet requests to the operator and forwarding their responses.
The high level gameplay corresponds to the core communications flow between Supplier and Operator APIs.
Note that the process is different for DEMO and REAL gameplay modes. In DEMO mode, user can open the game, check the rules/graphics/paytable, and play with fun mode money.
Below is an example of the interaction flow to open a game in DEMO mode:
Hub88 makes a call to the Supplier's Game API /game/url endpoint to obtain the game launch URL. You'll know that it's a DEMO mode call, as Hub88 will pass "currency":"XXX" and parameters token and user will be omitted.
When the game URL is returned, the Operator uses it to direct the user to the game (for example, launch it in iframe or redirect the user to the URL).
In DEMO mode, Hub88 doesn't expect any calls to Wallet API.
Below is an example of the interaction flow between the User, Operator, Hub88, and the game Supplier in REAL mode:
Hub88 generates and stores a unique game session token.
Hub88 makes a call to Supplier's Game API /game/url endpoint and passes the generated token along with the other request parameters.
Supplier is expected to respond with a valid game URL. When the game URL is returned, the Operator uses it to direct the user to the game (for example, launch it in an iframe or redirect the Operator to the URL).
When the game URL is loaded in the browser, the game Supplier's server makes a Wallet API call to Hub88/supplier/generic/v2/user/balance endpoint.
Hub88 verifies the token against the stored token and returns the user's balance. The user can then place a bet.
When the user attempts to place a bet, a Wallet API call /supplier/generic/v2/transaction/bet must be triggered on Hub88 server by the game Supplier.
Hub88 verifies the token, forwards the request to the Operator, who ensures that the user has enough money to place this bet. The Operator decreases the user's balance by the bet amount, and returns the updated user balance, which is forwarded as a response to the game Supplier.
If the user wins, the game Supplier is expected to trigger a /supplier/generic/v2/transaction/win call to Hub88 server using the Wallet API.
Hub88 verifies the token, forwards the request to the Operator, who ensures an increase in the user's balance by the win amount and returns the updated user balance, which is forwarded as a response to the game Supplier.
Behavior in case of user's loss depends on game Supplier's internal logic. Possible options:
Nothing is sent;
Sent win with amount 0.
