The AG Slots API brings 11 game providers into one content-discovery and game-session integration flow. Platform teams can use the provider catalog to organize game selection and browse 1,194 named catalog entries before mapping titles into their delivery plan.
Official website: https://aggameapi.com/
Last reviewed: 2026-08-09
| # | Game provider | Mapped games |
|---|---|---|
| 1 | PGSoft | 140 |
| 2 | Pragmatic | 457 |
| 3 | Evoplay | 63 |
| 4 | CP Games | 39 |
| 5 | WG Games | 34 |
| 6 | JILI | 94 |
| 7 | TADA | 78 |
| 8 | JDB | 59 |
| 9 | FC | 36 |
| 10 | BG | 93 |
| 11 | HSD | 101 |
Browse the complete provider-to-game catalog mapping or use the structured game catalog JSON.
The V5.0.0 game-content flow connects four practical steps:
- Provider discovery:
/game/v5/providersreturns the provider catalog used by the project. - Category discovery:
/game/v5/categoriesorganizes game types for navigation and selection. - Game listing:
/game/v5/gamesprovides paginated game discovery across the selected providers. - Game-session launch:
/game/v5/game/urlcreates a player session and returns the game launch URL.
This flow gives platform teams one integration model for provider selection, game discovery, and session launch across the 1,200+ game portfolio.
During project onboarding, AG and the platform team:
- select the provider and game scope for the first delivery;
- map game codes, categories, languages, currencies, and launch behavior;
- connect the selected wallet model and session return path;
- validate provider and game discovery in the test environment;
- verify the game-session and record flow before launch readiness.