Build with PlayerPal

Connect your casino or games to PlayerPal: link players without exchanging personal data, send activity and daily facts, and read analytics about your own players. Every integration is asynchronous, so nothing you build sits in the path of login, game launch, wagering or payouts.

15 minutesQuickstart

Sign a request, send your first batch and read a KPI back.

→ConceptsAuthentication

Request signing, partner tokens, the integration key and scopes.

→ReferenceAPI reference

Every partner endpoint, generated from the API's own code.

→

Choose your integration

OperatorsCasino integration

Let players link their casino account to PlayerPal, keep aliases in sync, and read analytics about your players.

1. Plan your integration
2. Authenticate
3. Link playersLink intent, player confirmation, result exchange
4. Send daily factsCommercial and attribution facts
5. Handle unlink notices
6. Read your KPIs

Start the operator path →

Game providersGame integration

Send settled rounds for points and analytics, show the PlayerPal widget in your games, and compare your studio with the network.

1. Plan your integration
2. Authenticate
3. Send activitySettled rounds in batches or bulk uploads
4. Send daily factsGameplay and game catalogue
5. Embed the widget
6. Read your KPIs

Start the game provider path →

Guides

PlayersLink players

Connect casino accounts and receive pairwise aliases.

→Data inSend activity

Settled rounds in JSON batches or bulk file uploads.

→Data inFact ingest

Daily gameplay, commercial, catalogue and attribution facts.

→AnalyticsKPI API

Your KPIs, breakdowns and anonymous network comparisons.

→PlayersWidget

Show PlayerPal inside your game pages.

→EventsWebhooks

Notices PlayerPal sends you, and how to reconcile.

→

Reference

Errors and idempotency

Every error code, retries and safe resends.

→Metric definitions

Grain, source, window and suppression for each KPI.

→Availability

How to integrate so play never depends on PlayerPal.

→Changelog

Changes to the partner API.

→

Tools

OpenAPI document	/openapi/partner.json: OpenAPI 3.1, for code generators and API clients
Code samples	curl, Node.js, Python, PHP, Java and C# on every guide. Your language choice is remembered across pages
For AI assistants	/llms.txt indexes every page; /llms-full.txt has all of it. Each page also has Copy page
Sandbox	Not available yet. Ask your PlayerPal contact about test credentials