LogoLogo
Knowledge BaseDeveloper DocsChangelogStatusNews
Developers Docs
Developers Docs
  • Hub88 APIs
    • Fundamentals
    • Core API flow
    • Request structure
    • Code samples
  • Operator API Reference
    • 🎲Operator API Overview
      • Error codes
      • Seamless Wallet response statuses - Operator API
    • Games API
    • Wallet API
    • TransferWallet API
    • Transactions API
    • Freebets API
    • Recommendations API
    • OnDemand API
  • Supplier API Reference
    • Supplier API Overview
      • Seamless Wallet response statuses - Supplier API
    • Games API
    • Wallet API
    • Freebets API
Powered by GitBook
LogoLogo

Hub88

  • HubWallet
  • HubMarket
  • Suppliers

Hub88

  • News
  • Status
  • Privacy Policy

Contact

  • sales@hub88.io

Follow us

  • LinkedIn
  • Telegram

Copyright © 2025. All Rights Reserved.

On this page

Was this helpful?

  1. Hub88 APIs

Core API flow

PreviousFundamentalsNextRequest structure

Last updated 3 months ago

Was this helpful?

Core communication flow between Supplier and Operator APIs

The entire data exchange flow goes through Hub88, because of this it's essential that an integration to either Operator API or Supplier API is built dependent on the use-case.

The data flow starts from player side, who chooses a game on online casino site (brand). This triggers calls from Operator side through Operator API to Hub88, which calls Suppliers through Supplier API, to get the necessary game contents (game_url).

Once the gameplay has started, Supplier needs to call Hub88 and update user balance based on the results and in-game activities. Hub88 then makes this data available for the Operator, which they are expected to display to the user.