Switch to Aggregator.gg
You run a casino on an aggregator and pay it a share of your gross gaming revenue. If that aggregator is Softswiss, SoftGamings, Soft2Bet, Hub88 or a smaller one, this page is for you. Every month the bill buys the same pipe: a wallet endpoint, signed callbacks, a catalog. When your players bet more, the bill grows. The pipe does not.
Aggregator.gg sells that pipe differently: prepaid packages at an agreed total. Compare the current offer with your own volume and contract rather than assuming a fixed saving. You do not have to switch to find out whether it fits. Open a second wallet endpoint beside the one you run today, prove the money path within confirmed access, credits and test limits, route the share of traffic you choose, and decide with your own numbers.
Write to us on Telegram if you want to talk about volume, brands, or your current contract before anyone touches code. Create a key and check your integration access when your team is ready to see the contract in its own cabinet.
What changed
Section titled “What changed”A rev-share bill tracks the wrong number. The aggregator takes a percentage of your gross gaming revenue. Raise the average bet and its bill rises with it, while the work it does for each round stays the same: one session, one callback, one settlement. Bet size moves the legacy bill. It never moves ours.
The integration itself is now one callback contract and a spec you can generate a client from. The price of the pipe no longer needs to be a share of your revenue. The scenario with the numbers behind this is on the pricing page.
What Aggregator.gg is
Section titled “What Aggregator.gg is”One API in front of many game studios. One production environment, one live agg_ key, one callback contract for every studio: bet, win, and refund on a single endpoint, amounts in your currency’s minor units, the new balance in the response. One catalog with RTP, volatility, and country metadata on every game.
You buy spins in packages at a fixed total, and the studios’ share is inside that total: nothing is billed on top for content. Setup is $0 and there is no monthly minimum. Free rounds settle through the same endpoint as paid spins.
Concept by concept, your current integration maps onto these terms on Switching aggregators.
Why operators switch
Section titled “Why operators switch”Compare the package with your actual bill
Section titled “Compare the package with your actual bill”Your bill stops depending on how much your players bet. A package is a number of spins for a fixed total, with the current package amounts shown in the cabinet and on the pricing page. Your finance team forecasts the cost of supply from traffic alone.
Savings depend on volume, stake, RTP and your current rev-share rate. Use your own figures and the current checkout offer. Platform-specific commercial terms can differ; ask support which offer applies to your organization.
Free-round transactions qualify for the non-billable categories only as specified by the Operator Service Offer, Schedule A. Inspect the recorded classification rather than assuming every promotional request has the same effect.
You migrate without a cutover date
Section titled “You migrate without a cutover date”Nothing in the integration touches the supply you run today. The endpoint for Aggregator.gg is new code at a new URL with its own secret; your current one keeps serving players. Before running real sessions, signed callbacks and settlement through the new path, confirm access, available credits and spending limits. A welcome grant may help if present; it does not guarantee a free test. The go-live checklist then gates the new path on money handling, security, and operations checks.
Both integrations serve traffic side by side for as long as the comparison is useful to you. The three steps are on Switching aggregators, the gate on Go live.
Check it yourself: Environments explains how to check a possible grant and test budget.
One contract for every studio
Section titled “One contract for every studio”Your team implements one normalized wallet contract. Paid bets, free bets, wins and refunds have distinct wallet effects. Deduplicate by trusted integration/organization, provider and transaction identity: replay the original response for a repeat with the same values, and answer a 4xx without moving money when the values differ. The response and retry contract distinguishes confirmed settlement, business declines, bounded transient retries and unknown outcomes requiring reconciliation.
Errors can be coded or flat; log fixed safe diagnostics and preserve operation identity during retries. API keys are replaced by overlap and revocation. Request limits are per key and per issuing user; see Rate limiting.
Check it yourself: the contract is on Callbacks, the envelope on Errors, the spec at /openapi.yaml.
You see what you buy before you sign
Section titled “You see what you buy before you sign”This hub prints no count of games, on purpose: a number would be stale before you read it. The studios behind the pipe are listed on aggregator.gg/supported-providers, no key needed. Create a key, call GET /v1/games, and you get the live catalog, every entry naming its studio (provider_code) with RTP, volatility, and country metadata, and filters for type, volatility, RTP, features, and currency. Before you route traffic, compare that list with your current lobby: the same studio may already serve you through both sides.
The rest is public too. The status page shows uptime and incident history without an account. The API Reference is generated from the same file you download at /openapi.yaml, byte for byte.
Check it yourself: open status.aggregator.gg now.
Proof you can check today
Section titled “Proof you can check today”Four things you can verify before you write to anyone.
- Open status.aggregator.gg. No account, no form.
- Download /openapi.yaml and generate a client. The file is byte-identical to the spec behind the API Reference.
- Create a key on API keys and call
GET /v1/games. That is the catalog your players would see today. - Review the wallet contract and plan implementation, tests and internal review against your own systems; these docs promise no universal completion time.
The Operator Service Offer publishes routing-layer SLA objectives and exclusions in Schedule B. Read those terms alongside status history.
How switching works
Section titled “How switching works”- Do it yourself. Register at app.aggregator.gg, create a key, confirm test access and budget, and follow the six-step track on Getting started with the migration shape from Switching aggregators.
- Talk to us. Volume above 500M spins, several brands, or a question about your current contract: write to us on Telegram with the facts.
- Convince your team. Send your CTO Switching aggregators and Callbacks. Send your finance lead the pricing page. Send both this page.
Resources
Section titled “Resources”- Economics: Pricing, Free rounds, Platform accounts
- Engineering: Switching aggregators, Callbacks, Errors, Environments, API keys, Go live, /openapi.yaml, API Reference, status.aggregator.gg
- Machine surfaces: llms.txt, MCP, Agent guidelines
Questions before you decide
Section titled “Questions before you decide”Engineering questions (contract stability, key rotation, client generation, AI agents doing the legwork) are answered on Switching aggregators. Below are the commercial ones.
What does it cost to start?
Section titled “What does it cost to start?”Nothing up front. Setup is $0, there is no monthly minimum, and a welcome grant may be available, but check the actual balance and limits before a money-path test. A paid purchase is confirmed by the server and matching credit when you buy your first package, and the ladder starts at a 100K-spin package; the terms are the Operator Service Offer.
How do I compare your price with what I pay in rev-share today?
Section titled “How do I compare your price with what I pay in rev-share today?”Take your last invoice and the number of spins behind it. Your rev-share bill followed bet size; a package follows spins. The four scenarios on the pricing page show the comparison at four volumes and four rev-share rates.
Do free rounds use up my package?
Section titled “Do free rounds use up my package?”For transactions that qualify under Schedule A.3 of the Operator Service Offer, free-round transactions flagged as non-billable under the API specification do not deduct from a package. Your team issues them with POST /v1/free-rounds; each round settles through the same callback, flagged is_free: true. Details on Free rounds.
Do I have to stop my current aggregator to start with you?
Section titled “Do I have to stop my current aggregator to start with you?”No. The integration is a second wallet endpoint beside the one you run today, and both serve traffic for as long as you want to compare them. The steps are on Switching aggregators.
I run several brands. One integration or several?
Section titled “I run several brands. One integration or several?”One. Several brands under one operator is a platform account: one key serves them all, each brand identified by sub_operator_ref with its own catalog and its own attribution; see Platform accounts. The cabinet may expose an organization-specific offer or its available package ladder; confirm the applicable platform terms with our team. The current wallet is shared at the parent platform, so confirm that configuration before testing brands.
Do I need KYB before I can try?
Section titled “Do I need KYB before I can try?”No. KYB is not a technical precondition for a key: you can create a working key and integrate while your file is still open, as API keys explains. KYB stays a compliance requirement before you operate on the platform, and live player traffic waits for the Go live checklist.