Core API Flow

Main communication flow between Provider and Operator APIs

All data exchange flow goes through the Bingão Hub, which is why it is essential to build an integration with either the Operator API or the Game Provider API depending on the use case.

The data flow starts from the player's side, who chooses a game on the BET MGM website. This triggers calls from the Operator side through the Operator API, which in turn calls the Providers through the Game Provider API to obtain the necessary game content (game_url).

Once the game has started, the Provider needs to call the Bingão Hub and update the user's balance based on the results and in-game activities. The Bingão Hub then makes this data available to the Operator, who is expected to display it to the user.

• User/Player Browser: The user connects to the BET MGM operator through a web browser, where they can register or log in..

• Operator (BET MGM): After authentication, the BET MGM operator manages the user's session, including balance verification and navigation between rooms.

• HUB (Bingão): BET MGM communicates with the integration HUB, sending user data (player ID, balance, preferences) and receiving information about available rooms, prizes, and real-time events.

• Game Provider (Bingo Maker): The HUB integrates with the Provider, where game requests are processed. The Bingo Maker provides game mechanics, results, and prize distribution back to BET MGM.

High level overview of Core API flow