Rewards
Introduction
Unibo requires a dedicated endpoint to facilitate prize payouts for rewards that are issued on your provider and credited to the player’s account.
The Rewards integration enables Unibo to trigger rewards using the reward functionality already available on your provider (e.g. free spins and cash. Unibo does not manage player balances directly — you 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 provider reward scope.
Provider-Paid Rewards
Provider-paid rewards are rewards that:
Are issued by your provider
Are credited directly to the player’s account
Are executed via your existing reward or wallet APIs
Typical examples are Cash and Free Spins.
For these rewards, Unibo will trigger a payout request to your provider when campaign conditions are met.
Catalog Rewards
Catalog rewards are defined and managed in Unibo and do not require an automated payout via provider APIs.
They are used for rewards that are paid out manually or fall outside the standard provider reward capabilities. Depending on provider setup, catalog rewards may be mapped to provider bonuses outside of the standard automated payout flow.
No additional endpoints are required for catalog rewards.
Key Requirements (Provider-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
Parameter-Based Payouts (No Predefined Rewards)
Other providers 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"
}Periodic Synchronisation
Unibo periodically synchronizes provider-paid rewards with its local state.
Rewards that become unavailable on the provider are marked accordingly.