Play'n GO API integration
Explore Play'n GO API integration through Aggregator, including PlaynGo catalogue naming, category interpretation and production access checks.
This guide describes access through Aggregator, not a direct provider API or an official partnership. Catalogue visibility does not confirm production entitlement, provider endorsement or permission to operate in any territory.
Current catalogue records
- Catalogue entries
- 392
- Catalogue feeds
- 1
- Snapshot updated
Counts describe cached catalogue records, not guaranteed unique games. Regional feeds may overlap. Refreshes can change the figures; use workspace discovery for actual access.
Source feed names
- PlaynGo
Source category breakdown
- Arcade: 1 entries
- Bingo: 3 entries
- flash: 234 entries
- Poker: 2 entries
- Slot: 1 entries
- Slots: 142 entries
- table: 9 entries
Labels are source metadata, not verified game capabilities.
Map the display brand to catalogue records
The directory displays PlaynGo records as Play'n GO. This presentation alias is not a game-ID conversion rule. Preserve the exact identifier returned by the API, including its brand and game components, when storing catalogue choices or sending launch requests.
Review the raw category breakdown before building filters. Source categories can include legacy technology labels alongside game categories; these do not prove current browser compatibility. Test selected games on your supported browsers and confirm currencies and feature flags with the enabled catalogue.
From catalogue discovery to wallet settlement
- Create a workspace and keep your X-API-Key on your backend. Confirm provider, game and currency enablement.
- Call getGameList for the intended play currency. Copy the returned identifier exactly; do not construct it from the brand or feed name.
- Test demo launches where supported. For production launches, reserve player funds and retain the request with its idempotency key.
- Validate signed settlement callbacks, duplicate handling and unknown outcomes before completing the production checklist.
Currency, territory and commercial access
The public snapshot does not establish supported currencies or territories for your account. Confirm these with the team and your workspace entitlements. A regional feed name is not regulatory approval. Provider and game restrictions still apply after activation.
Compare activation plans and estimate GGR fees. Activation, player balances and GGR funding are separate; estimates are not invoices or currency conversions.