Provider onboarding
You bring games; the operators on the network bring players. Aggregator.gg sits between the two: operators integrate once against one canonical contract, and every studio’s protocol is connected to that contract by our team, together with yours. This page is the map of that work: what the integration looks like, the stages it moves through, and what to have ready before the first call.
How integration works
Section titled “How integration works”Provider integration is assisted. You do not rewrite your game server against our API: our team builds a connector for your protocol, and each provider’s launch protocol, callback shape, and signature scheme is translated into one canonical contract. The connector meets your protocol where it is; the work between your team and ours is agreeing the mapping and proving it holds.
That one contract is why the model pays off. Operators on the network already speak it, so once your connector is live, eligible operators can enable your games without a separate connector project. Availability still depends on provider and account enablement, jurisdiction and agreed commercial access.
Three pages describe your side of the contract in detail:
- Catalog requirements: the game metadata operators see and filter by.
- Runtime expectations: what your game server handles in production.
- Certification and go-live: the joint test run before traffic opens.
The five stages
Section titled “The five stages”Integration moves through five stages, and each one gates the next.
- Introductions and documentation. We exchange documentation: you get these pages, we get your protocol specification, your auth model, and a technical contact on your side.
- Catalog and metadata. You hand over the list of games you want distributed, with the metadata described in Catalog requirements, including RTP with its source named.
- Connector and test bench. Our team builds the connector against your specification. Your team keeps a test environment of your game server reachable, and we wire launch, session, bet, and win end to end against our staging before anything touches production.
- Certification run. Together we run the happy path and the failure scenarios on a sandbox operator with a test player, as described in Certification and go-live.
- Open traffic. Your games become visible to operators, and both teams watch the first live sessions.
Who does what
Section titled “Who does what”| Stage | Your team | Our team |
|---|---|---|
| Documentation | Shares the protocol spec, auth model, and test credentials; names a technical contact | Reads it, maps it to the canonical contract, comes back with questions |
| Catalog | Assembles the game list and metadata; names the source behind each RTP | Validates the metadata, loads the catalog, flags gaps |
| Connector | Keeps the test bench reachable; answers protocol questions | Builds the connector and wires it against staging |
| Certification | Drives your side of the run; fixes findings in your protocol or game server | Drives the scenarios; fixes findings on the platform side; reconciles the run |
| Open traffic | Watches your first live sessions and launch answers | Watches the platform side and opens operators gradually |
What to prepare
Section titled “What to prepare”The integration starts moving as soon as these exist. None of them need to be perfect on day one; they need to be real.
- A game catalog with metadata. The games you want distributed, with the fields from Catalog requirements. RTP arrives with its source named; silent defaults are not accepted.
- Protocol documentation. The specification of your launch, session, and money calls: endpoints, payloads, auth, and signatures, as they actually behave.
- A reachable test environment. A staging instance of your game server we can integrate against, with test credentials.
- A technical contact. One named engineer on your side who can answer protocol questions while the connector is built.
Your first step
Section titled “Your first step”Write to support@aggregator.gg with your game catalog and a technical contact, and tell us in a couple of sentences how your protocol works. We read everything and come back with the questions that start stage one.