Bonus API
Bonus APIs connect eligibility decisions, promotional rewards and lifecycle events with the player and gaming systems.
The integration in practice
Promotions should be traceable from qualification through award and expiry. The platform must distinguish promotional balances from real-money transactions where relevant.
Core interface requirements
- Campaign identifiers, audience eligibility and activation rules.
- Reward issuance, progress updates and bonus balance events.
- Expiry, cancellation and completion or conversion states.
- Abuse controls, event tracking and reporting for operations.
The specific bonus mechanics depend on the platform, game provider requirements and applicable market rules.
How this connection takes shape
These steps describe the technical questions to resolve. The final implementation and deliverables are defined from the actual systems involved.
Specify eligibility
Describe who may receive a campaign, how consent and restrictions apply and which service makes the final qualification decision.
Model bonus states
Define issuance, activation, progress, wagering conditions, expiry and cancellation as auditable transitions.
Link rewards to finance
Distinguish cash and promotional balances where required, and record how rewards interact with the wallet and reporting.
What we need to review
- Campaign types, qualification and exclusion rules
- Bonus and real-money balance ownership
- Events available from the game provider or sportsbook
Acceptance cases to plan
- An ineligible player cannot activate a promotion through a repeated request.
- An expired award is not redeemed after an out-of-order progress event.
- A campaign’s issued and redeemed totals reconcile with wallet movements.
Questions to resolve before delivery
Can bonuses use third-party game events?
Only when the provider exposes suitable events and their terms permit the intended mechanic.
How should an expired bonus behave?
Expiry must be reflected consistently in eligibility, balance and transaction records. The exact flow follows your product rules.
Can eligibility depend on player activity?
Only if the required events and lawful permissions exist. The frequency and trustworthiness of those signals are part of the scope.
Can two promotions overlap?
That depends on the campaign engine and business rules. Priority, stacking and conflict resolution must be specified before development.