Skip to main content

Operator API Integration

Unlike the Platform and Frontend APIs — which your systems call into the Gamanza Engage Platform (PEP) — the Operator API is the set of endpoints you implement on your side so that PEP can call out to you. PEP uses them to validate player sessions, credit bonuses and cash, synchronize game metadata, reconcile player data, and report the outcome of player migrations.

Each API below is published as its own OpenAPI spec. Open its Introduction page for the full request/response reference, and use the Export button there to download the spec (for example to scaffold the endpoint or generate a server stub).

tip

For the step-by-step integration walkthrough — authentication setup, when each endpoint is called, and worked examples — see the Operator API integration guide.

APIs you implement​

  • Validate Player Identity Token — validate a player's session (SSO-style) and return the playerId so PEP can authorize the player for the Frontend API and UI Widgets. Required for any player-facing gamification.
  • Bonus API — let PEP credit bonuses to players and read the bonuses available in your bonus system.
  • Cash API — let PEP credit cash to players, for example as a loyalty reward or CRM campaign payout.
  • Games Metadata — expose your game catalog so PEP can synchronize game metadata into the platform.
  • Players Migration — webhook PEP calls to deliver the outcome of a completed player migration or offline-data-update batch.
  • Reconciliation API — let PEP request a sync of missing player or responsible-gaming data, as a fail-safe to keep your platform and PEP aligned.