Fast casino API integration: a first game launch in one day

Where the time actually goes in a casino API integration

Ask an engineer how long a game aggregator integration takes and the answer is usually a few days of code. Ask the operator how long it took from first email to first real bet and the answer is often several weeks. The gap is almost never the API. It is everything around it:

• The sales cycle. A discovery call, a proposal, a negotiation, then a contract round on both sides before anyone gets a sandbox.
• Paying to get started. A setup or integration fee invoiced up front, and nobody receives credentials until it clears.
• Waiting for the sandbox. Staging keys requested by ticket, then production keys requested again later, with a separate review in between.
• A wallet spec with surprises. Bonus wins without a matching bet, rollbacks, unknown transaction types that the operator's handler rejects and the vendor treats as an error.
• Currency provisioning. The player currency turns out not to be enabled, and launches fail until someone on the vendor side switches it on.

SoftAggregator was built to take the first three off the table entirely and to document the last two in advance, so the only work left is the operator's own code.

Day 0: signup to working API keys

• Sign up on the SoftAggregator portal and choose the account currency.
• Receive api_login, api_password and salt_key the same day, in the operator backend.
• Set the callback URL, and allowlist the fixed source address of the callbacks, 85.122.129.59.
• Test credit is on the account, so games can be opened for real before any top-up.
• No contract round, no setup fee, no integration fee, no monthly fee.

Day 1: the first real launch

A developer who already runs a player wallet can do this in an afternoon, in this order:

1. getCurrencies: confirm which player currencies are enabled on the account, so the launch does not fail on a currency mismatch.
2. getGameList: pull the catalogue; build the lobby from the normalised game_type field (slots, live, crash, table, sportsbook and so on), not from the raw studio labels.
3. createPlayer: create one test player with its currency, which is fixed for that player from then on.
4. Callback handler: answer balance, debit and credit with HTTP 200 and a JSON body, amounts in cents, de-duplicating on call_id. Validate key = md5(timestamp + salt_key), or the stronger X-Signature HMAC header.
5. getGame: request a launch URL for one slot, open it in an iframe, place a bet and watch the debit and the credit arrive.
6. getPlayerHistory: check that the round you just played is there with the right bet and win.

Two rules save most of the debugging time, and they are written in the documentation for that reason: never reject a callback because of its type field, and accept a credit that has no matching debit, because free spins, bonus rounds and jackpots pay out that way.

Week 1: from one game to a production lobby

• Load the full catalogue and the studio list (getProviderList), and decide which studios and categories to feature: Pragmatic Play, Evolution, PG Soft, Hacksaw Gaming, Aviator and the crash category, and so on.
• Add live casino and, if wanted, the sportsbook. Both use the same getGame call and the same callbacks, so this is front-end work, not a second integration.
• Pass device: mobile on mobile launches and the player's language in lang.
• Use getGameDemo for a play-for-fun mode on the lobby, no wallet calls involved.
• Load the prepaid balance (USDT and other supported currencies) and switch real players on. Commission is deducted from that balance as a share of GGR: 8% casino, 9% sportsbook, 11% live casino.
• Running several brands? Each extra site gets its own keys and callback URL on the same account, without a new integration project.

How this compares with the rest of the market

Speed claims in this market are hard to compare because vendors measure different things. Some aggregators publish fast go-live figures; Hub88, for example, publishes go-live in as little as three days. Enterprise platforms usually run a sales-led onboarding with commercial terms discussed during the process, and several weeks between first contact and live traffic is a common outcome, most of it spent before any code is written.

The fair comparison is therefore not "days of coding" but "days until a developer can open a real game". On that measure SoftAggregator's figure is the same day: keys and test credit on signup, public documentation at softaggregator.com/docs.html that can be read before signing up, and no invoice to wait for.

A team without an existing wallet should count the time to build one; that part is the operator's platform, not the game API, and no aggregator can shorten it.

Fast casino API integration — FAQ

Explore more