Rewards
How Unibo issues prize payouts to players
Unibo does not manage player balances directly — your platform remains the source of truth. When a player earns a prize from a campaign, mission, or tournament, Unibo calls your platform's API to issue the reward.
Reward types
Platform-paid rewards
Issued through your platform's APIs. Includes cash, bonus money, free spins, and loyalty points. Your platform processes these automatically. For these rewards, Unibo will trigger a payout request to your platform when campaign conditions are met.
Catalog rewards
Defined within Unibo itself. Typically require manual payout or fall outside standard automation. No additional endpoints are required for catalog rewards.
Integration requirements
Authorization
Your platform's reward API needs to support:
Authentication — API key in a header, or IP allowlist.
Idempotency — a unique identifier per payout, so Unibo can retry safely without creating duplicates.
Payout approaches
Two patterns are supported. The exact schema is agreed during integration kickoff; the snippets below are representative.
Template-based
Unibo references a predefined bonus program on your platform and supplies dynamic parameters.
{
"templateId": "welcome-bonus-tier-1",
"playerId": "StQ-1",
"transactionId": "po_9cd823d3fe",
"amount": 5.00,
"currency": "EUR"
}Parameter-based
Unibo sends all the fields needed to construct the reward inline.
{
"type": "CASH",
"playerId": "StQ-1",
"transactionId": "po_9cd823d3fe",
"amount": 5.00,
"currency": "EUR"
}Jackpot and dynamic rewards
Jackpot campaigns and other dynamic reward types require your platform to support variable prize values and multiple currencies. Confirm support during integration kickoff.
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
Synchronization
Unibo periodically synchronizes platform rewards to keep its catalog aligned with your system's current state.
Lifecycle webhooks
Unibo sends webhooks for the lifecycle of every payout (PRIZE_PAYOUT_CREATED, PRIZE_PAYOUT_SUCCEEDED, PRIZE_PAYOUT_FAILED, PRIZE_PAYOUT_BLOCKED)
See Webhooks for the full event reference and integration guide.