Hub88

Most aggregator reviews start with game counts. This Hub88 review starts with the docs, because that is where the Hub88 aggregator is most convincing. Hub88 advertises 26,000+ games (site, October 2026), but what sets it apart is how clearly the wallet contract is written down and how strictly calls are signed.

The Hub88 aggregator API, read like an engineer

Hub88 publishes an operator API reference you can study before any call with sales. The parts worth reading first:

• Wallet API. Hub88 calls your endpoints to read and change player balances. This is the classic seamless model.
• TransferWallet. An alternative where funds move into the game session rather than being debited live. Useful if your platform cannot expose a fast balance endpoint.
• Games API. Your calls to Hub88 to list and launch games.
• Freebets API. Grants free spins, free bets or prizes to one user or a batch of users.

Signing, both ways

Every request body is signed with RSA-SHA256 and Base64-encoded into the X-Hub88-Signature header (docs, October 2026). You sign Games API and TransferWallet calls with your private key. Hub88 signs Wallet API calls, and you verify them with Hub88’s public key.

The docs add a detail that catches teams out: verify against the raw body bytes before parsing JSON. Re-serialising the body, even adding one space, breaks the signature. Put that in your integration ticket on day one.

Scenario: a mid-size crypto casino with its own backend

A team of six engineers runs one casino on a custom backend. They want a second aggregator to cover studios their first one lacks, and they want promos without building a bonus engine.

Hub88 fits. The wallet contract is precise enough to build against in parallel with the commercial talks, and the Freebets API lets the CRM team push free spins from a script. The signing scheme is stricter than the HMAC shared secrets many vendors use, which security reviewers tend to like.

What this team will miss: a public studio list to check overlap with the first aggregator. Ask for it before writing code.

A pre-build checklist for your engineers

Before the first commit, write test cases for these:

• Signature verification on raw bytes. Feed a body with an extra space and confirm your verifier rejects it.
• Key handling. Generate the key pair the way the docs describe (openssl genrsa, then openssl rsa -pubout), store the private key outside the repo and plan rotation.
• Idempotency. The same transaction arriving twice must not move money twice.
• Rollbacks. A bet that timed out on your side and was later rolled back by Hub88 must leave the balance exactly where it started.
• Freebets accounting. Decide how a free-spin win lands in the player’s balance and how your bonus rules treat it.
• Currency field. The docs examples carry a currency code such as EUR in each request. Map every currency you plan to offer before launch.

Teams that settle these six items early usually spend their certification week on edge cases rather than on rewrites.

What to ask Hub88

1. The full provider list, as a spreadsheet, with launch dates for new studios.
2. Which currencies each provider settles in, including crypto.
3. Revenue share per vertical and any monthly minimum.
4. Freebets: which providers support them, and are they free to the operator?
5. Retry and rollback rules when your wallet times out.
6. Seamless or TransferWallet: which do most clients on your stack use, and why?

Where Hub88 falls short

The homepage is thin on numbers: no provider count, a 200+ currencies total with no list behind it, no pricing (October 2026). Onboarding goes through [email protected], so there is no instant sandbox. And engagement tools beyond the Freebets API are not as visible as the tournament and jackpot suites at SOFTSWISS or Pariplay.

Who else to shortlist

If the public docs are what drew you to Hub88, put St8 next to it for the same reason. If the first launch date matters more than reading docs in advance, SoftAggregator is the other obvious name: self-service sign-up, keys the same day and 40,000+ games from 200+ studios (site, October 2026), against the 26,000+ on Hub88’s aggregator page. Hub88 keeps the edge on documentation and request signing. SoftAggregator answers two of the gaps listed above: it publishes a catalogue figure, and it states its fee position openly (no setup, integration or monthly fee). For engagement tools, SOFTSWISS remains the reference. The two are set side by side in SoftAggregator vs Hub88.

The GambleGames take

Hub88 scores 7.8. Its API and wallet mark is the highest in this group, thanks to public docs and signed requests in both directions. Catalogue and cost of entry hold it back: no published studio list and no published pricing. If you want a second opinion on the API side, compare it with St8 in St8 vs Hub88, or with Slotegrator in Hub88 vs Slotegrator. Our casino API integration checklist lists the wallet questions to settle first.