Unibo
Integration

Rewards

Introduction

Unibo requires a dedicated endpoint to facilitate prize payouts for rewards that are issued on your platform and credited to the player’s account.

The Rewards integration enables Unibo to trigger rewards using the bonus and reward functionality already available on your platform (e.g. free spins, bonus money, cash, loyalty points). Unibo does not manage player balances directly — your platform remains the source of truth for reward creation, issuance, and accounting.

In addition, Unibo supports a separate Catalog reward type, allowing you to create additional rewards outside of the standard platform reward scope.

Platform-Paid Rewards

Platform-paid rewards are rewards that:

  • Are issued by your platform

  • Are credited directly to the player’s account

  • Are executed via your existing reward, bonus, or wallet APIs

Typical examples include:

  • Cash

  • Bonus money

  • Deposit bonuses

  • Free spins

  • Free bets

  • Loyalty points

  • Loot boxes or similar account-based rewards

For these rewards, Unibo will trigger a payout request to your platform when campaign conditions are met.

Catalog Rewards

Catalog rewards are defined and managed in Unibo and do not require an automated payout via platform APIs.

They are used for rewards that are paid out manually or fall outside the standard platform reward capabilities. Depending on platform setup, catalog rewards may be mapped to platform bonuses outside of the standard automated payout flow.

No additional endpoints are required for catalog rewards.

Key Requirements (Platform-Paid Rewards Only)

Authorization

Unibo supports:

  • API key–based authorization (via request headers), or

  • IP whitelisting

Idempotency

To prevent duplicate payouts:

  • Each payout request includes a unique identifier

  • Duplicate requests with the same identifier must not result in multiple payouts

Payout Request Patterns

Platforms differ in how rewards are issued. Unibo supports both of the following payout patterns for platform-paid rewards, and the exact approach is aligned during integration.

Template-Based Payouts (Predefined Rewards)

Some platforms require a reference to a predefined reward or bonus program/template when issuing a payout. In this case, Unibo sends a reference along with any dynamic parameters required (e.g., amount).

{
  "playerId": "7003",
  "rewardRef": "BONUS_1153",
  "amount": 50.0,
  "currency": "USD",
  "transactionId": "29f8b061-3e6c-4e66-9848-c980d1c725b1"
}

Parameter-Based Payouts (No Predefined Rewards)

Other platforms expose dedicated endpoints per reward type and require Unibo to send all necessary parameters to issue the reward.

{
  "playerId": "7003",
  "rewardType": "CASH",
  "amount": 50.0,
  "currency": "USD",
  "transactionId": "29f8b061-3e6c-4e66-9848-c980d1c725b1"
}

Jackpot & Dynamic Rewards

  • To support jackpot campaigns with variable prize values, the platform must support:

  • Dynamic reward values per player

  • Multiple currencies, where applicable

Depending on platform capabilities, dynamic cash payouts may be handled by:

  • Allowing dynamic amounts on a predefined reward template, or

  • Exposing a payout endpoint that does not rely on predefined reward configuration

Periodic Synchronisation

  • Unibo periodically synchronizes platform-paid rewards with its local state.

  • Rewards that become unavailable on the platform are marked accordingly.

Was this helpful?