Sample iGaming Gamification Event Payloads

Ludora receives player activity via a REST event API. Below are illustrative JSON payload structures for the most common event types operators send during integration.

All events include a player identifier, event type, timestamp, and relevant metadata (amount, game ID, market, etc.). Ludora evaluates each event against active mission and tournament rules in real time.

• casino_bet: Triggered on any casino spin or bet placement.
• sportsbook_bet: Triggered on pre-match or live bet placement.
• deposit: Triggered on confirmed player deposit.
• registration: Triggered on new player account creation.
• custom_event: Operator-defined events for platform-specific actions.

Frequently Asked Questions

What format does the Ludora event API use?

Ludora uses a JSON REST API. Events are POST requests with a structured payload including player ID, event type, timestamp, and contextual metadata.

Can operators send custom events to Ludora?

Yes. Ludora supports operator-defined custom event types, allowing any platform-specific action to trigger gamification rules.