Unibo
Operator/Platform Integration

Integration FAQ

The short version: you send us events, we send you payouts, and two script tags to integrate on the frontend. Unibo runs the campaigns, leaderboards, prize logic, notifications and backoffice.

Loading custom HTML embed

What's required?

Three things. Nothing else.

1. Event stream (you call us)
One endpoint, one API key per brand, JSON batches.

POST https://consumer.unibo.io/api/v1/events
x-api-key: <your brand key>

2. Rewards endpoint (we call you)
When a player wins a prize, Unibo calls your API with the player id, the reward, amount, currency and a unique reference. You credit the player. Auth is an API key header or an IP allow-list.

3. Widgets (script tags)
Set required cookies per integration type and load one script per widget. Each widget mounts itself.

How long does the integration take?

About one week end-to-end.

Piece

What you build

Effort

Event stream

Forward bets and wins to one Unibo endpoint

1–2 days

Rewards

One endpoint on your side that credits a bonus or free spins

1–2 days

Players & games

Send player and game events on the same stream

Hours

Widgets

Script tags

Hours

General FAQs

What should be included in a game round?

Two events per round, a bet and a win, sharing the same round_id. Nine fields, all required:

{
  "event": "gameround",
  "data": {
    "unique_id": "bet-f7ltid",
    "timestamp": "2025-01-15T12:00:00Z",
    "player_id": "StQ-1",
    "game_id": "GD8",
    "round_id": "f7ltid",
    "amount": 0.5,
    "currency": "EUR",
    "is_win": false,
    "is_bonus": false
  }
}

  • timestamp is when the bet happened, in UTC. Not when you sent it.

  • amount is a positive number. currency is an ISO-4217 code.

  • The win is the same event again with is_win: true.

Do you need to send deposit events?

Optional. Campaigns work without them. Send them if you want to use deposit tasks and have better campaign reporting.

Same endpoint, "event": "deposit", with player_id, amount, currency and method.

Do you need a separate API for games and players?

Optional. Send player and game events on the same stream: one initial seed of what you have, then updates as they happen.

Unibo stores only your IDs, never names or emails. A pull API on your side is optional and used only for reconciliation.

What prizes can Unibo pay out?

Anything your rewards API can credit today. Cash, free spins, bonus money etc.

We map your reward IDs into the Unibo backoffice. Every payout carries a unique reference, so a retried call never pays twice. Prizes your API cannot issue can still exist as manually handled catalog prizes.

How do we add the UI?

Pick one or both

  • Campaign Dashboard on your site: lobby, promotions page, any button you choose. Shows all campaigns, leaderboards, prizes and opt-in.

  • In-Game Widget on your game page, wrapped around the game iframe. Shows live progress for the campaigns played, beside the game on desktop, over it on mobile.

The smallest example, the Campaign Dashboard:

<script>
  document.cookie = "unibo_userId=player_123; path=/;";
  document.cookie = "unibo_registrationDate=1690675200; path=/;";
</script>
<button id="unibo-osw-custom-1">Tournaments</button>
<script src="https://<brand>.widgets.unibo.io/on-site/widget.js"></script>

Ready to get started?

Pick the guide that matches your next step.

Was this helpful?
Was this helpful?