Developers

Developer Docs

Learn how to connect your casino platform to Syncora for player events, CRM automation, bonus orchestration, and player engagement.

Start here

Overview

Syncora sits alongside your casino platform. Your backend streams player events; Syncora turns them into CRM journeys, segments, analytics, bonus orchestration, and gamification.

Ingest

Your PAM posts player events to /api/public/v1/ingest.

Process

Syncora resolves the player, updates the profile, and runs CRM logic.

Activate

Journeys, segments, bonuses, and analytics act on the new signal.

Core concepts

Partner

Your casino brand or operator tenant in Syncora. All data is isolated per partner.

Player

A person in your platform, identified by an external ID from your casino/PAM.

Event

A signal about player activity — login, deposit, bet, KYC change, and more.

Journey

An automated flow triggered by events, with steps, waits, and actions.

Segment

A dynamic audience defined by player attributes and behavior.

Bonus

A CRM bonus definition or grant. Fulfilment happens on your PAM.

Widget Token

Short-lived, player-scoped token for browser-side widget access.

API Key

Server-side credential for partner backends. Never expose in browsers.

API keys are for partner servers only. They must never appear in browser or frontend code. For player-facing browser access, use short-lived widget tokens minted server-side.

Basic integration flow

A typical partner integration looks like this.

Step 1

Create or retrieve your API key

Provision a partner API key inside Syncora. Store it in your backend secret manager.

Step 2

Configure your casino/PAM backend

Add the API key to your backend environment. Never ship it to the browser.

Step 3

Send player events

POST events to /api/public/v1/ingest as they happen.

Step 4

Fetch player state

Use /api/public/v1/player/:id when you need Syncora's view of a player.

Step 5

Connect bonus fulfilment

If your PAM supports bonuses, wire grants through /api/public/v1/grant-bonus.

Step 6

Test in the Event Inspector

Verify ingest, journeys, and bonus actions in the Syncora Event Inspector.

Supported event examples

Send events with the canonical shape used by the ingest endpoint.

login

Player logged into your casino. Send registration as login with data.registration = true.

deposit

Successful deposit with amount and currency in the event payload.

bet

Wager placed. Include amount, currency, and optional game context.

win

Winning outcome. Include amount and currency.

kyc_change

KYC status update. Include the canonical status in the payload.

bonus_claimed

Player claimed or consumed a bonus (sent via free_spin_used or related events).

Example event payloadjson

{
  "player_id": "ext_123",
  "type": "deposit",
  "data": {
    "amount": 50,
    "currency": "EUR",
    "status": "completed"
  }
}

Registration is currently sent as type: "login" with data.registration = true. Include email, country, and language in data when available.

Next steps

Ready to connect your casino platform? Walk through the integration guide or talk to our team.

View Integration Guide Contact Sales

Ready to connect your casino platform?

See a live walkthrough of Syncora with your team.

Book a Demo