Aggregation Platform Documentation
Welcome!
The Aggregation Platform is designed to make collaboration between Game Providers and Game Operators simpler, more consistent, and easier to scale. In a fragmented ecosystem, bringing game content to market can easily become a network of one-off integrations, custom workflows, and duplicated effort. An aggregation model replaces that complexity with a shared integration layer and a common operating model.
In practical terms, this means that Game Providers can connect their games and game engines to a broader distribution channel, while Game Operators can make a wider portfolio of content available to their players through their own products and channels.
The Main Roles in the Ecosystem
At the center of this ecosystem are two main types of partners:
- Game Providers, who develop and operate the games or game engines that deliver the gameplay experience.
- Game Operators, who offer those games to their players through their own websites, apps, portals, or retail channels.
Game Operators usually own the player relationship end to end. This often includes the player account environment, the wallet domain, and the lobby where players discover and launch content. Game Providers, in turn, focus on the game content itself and on the systems required to run the underlying game logic.
What the Aggregation Platform Does
The role of the Aggregation Platform is to provide the shared layer that allows these actors to work together through a more consistent model. It helps reduce integration friction, creates a common language across different participants, and supports a more structured path from onboarding to live operations.
Depending on the integration flow, this can include:
- exposing game catalogs to Operators;
- orchestrating launch and session flows;
- providing session context to Game Providers;
- supporting wallet, gameplay, and reporting interactions;
- standardizing the contracts used across the ecosystem.
This portal focuses on that shared model. It explains the roles involved, the main API contracts, and the integration guides that help Operators and Providers move from onboarding to implementation.
How to Use This Documentation
Different readers usually arrive here with different goals:
- If you are a Game Operator, the Game Operator guide is the best starting point.
- If you are a Game Provider, begin with the Game Provider guide.
- If you want a broader introduction to the platform model, continue with the Overview.
- If you want to inspect the API contract in detail, explore the API reference sections.
- If you want to understand the conventions behind the API design, the API guidelines provide the broader design context.
A Shared Integration Language
One of the main goals of an Aggregation Platform is to create a shared integration language across the ecosystem. Even when Operators and Providers have very different internal systems, a common API model makes collaboration easier to understand, easier to maintain, and easier to scale over time.
That is the purpose of this portal: to provide a clear entry point into the platform, help you navigate the relevant materials, and support a more structured integration journey for every partner involved.