Pragmatic Play API integration
Plan Pragmatic Play API integration through Aggregator: compare regional and live catalogue feeds, check currency access and validate game launches.
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
- 1,988
- Catalogue feeds
- 4
- 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
- PragmaticPlay-Asia
- PragmaticPlay-EU
- PragmaticPlayLive-Asia
- PragmaticPlayLive-EU
Source category breakdown
- Arcade Game: 2 entries
- Casino: 3 entries
- Casino Live: 157 entries
- CasinoLive: 137 entries
- Classic Games: 5 entries
- Crash: 1 entries
- Crash Game: 1 entries
- HotSlots: 622 entries
- Live: 170 entries
- MiniGames: 7 entries
- other: 2 entries
- Slot: 180 entries
- Slots: 696 entries
- Table Games: 5 entries
Labels are source metadata, not verified game capabilities.
Separate regional and live feeds
The directory groups Pragmatic Play regional and live feeds under one brand. A grouped total can include the same title in more than one feed; it is not a unique-game count. Select the exact game identifier returned for your enabled currency rather than translating a title or a regional feed name into an identifier.
Review live and non-live entries separately with your team. A regional label does not grant permission to operate in that region, and access to one feed does not prove access to another. Confirm the requested products and markets before testing launch and settlement behavior.
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.