Core Functionality
Integration Adapters
Upstream systems can send any payload shape they already support. Inbound adapters transform those events into the platform model, then outbound reward adapters execute fulfilment-specific behavior to complete each reward reliably.
Inbound event adapters
Different operators can submit event payloads in their own shape. Select a source to see how an adapter maps it into the gamifi.me canonical event.
Operator Event Payload
Inbound Adapter
Canonical Event Model
Operator A · JSON API
Operator B · XML Feed
Operator C · CSV Batch
Operator D · Custom Fields
Sample source payload
Adapter transform output
Mapping rules
Click an operator format card to inspect the transformation
Interactive reward fulfilment adapters
Select a reward route to inspect adapter behavior, player outcome and business benefits.
Play & win
Reward earned
Fulfilment engine
Select a delivery route below
- Play & win: Player activity in a tournament determines winners.
- Reward earned: Winning outcomes are finalized and reward intent is created.
- Fulfilment engine: Routes each reward to the correct adapter with tracking and retries.
Gift card
Adapter procures voucher
Email delivered to player
Redeemed on Amazon
Operator wallet
Adapter credits account
Balance updated instantly
Used for in-game play
Promo spins
Adapter grants free spins
Credited to player account
Consumed in game rounds
Retail
Adapter places order
Item purchased for player
Physical delivery arranged
Player outcome
Click any route card above to explore it
Why this model scales
- Source systems do not need to rewrite payload contracts to join tournaments.
- Transformation logic is isolated in adapters, so core ranking logic stays stable.
- Each reward adapter can implement retries, callbacks, and completion checks per channel.