Crash games API: Aviator, JetX and the multiplier genre in one integration

What is a crash games API?

A crash games API is the integration that puts multiplier games such as Aviator and JetX in your lobby: one call lists the titles, one call returns a launch URL, and your wallet receives a debit when the player bets and a credit when the player cashes out. Through SoftAggregator, crash titles live inside the catalogue of our casino game aggregator API, so there is no second contract and no second wallet to build.

Crash is the fastest-growing casual format in online casinos since 2019. A round lasts seconds, the rules fit in one sentence, and the social layer (other players’ bets and cash-outs scrolling live) makes it feel like a shared event rather than a solitary spin. For an operator it is also the vertical with the tightest timing: a slow wallet endpoint is felt by the player within the same round.

How a crash round works

Every crash game follows the same loop. A betting window opens for a few seconds. When it closes, a multiplier starts at 1.00x and climbs. At a point decided before the round began, it “crashes”. Anyone who cashed out before that point is paid stake × multiplier; anyone still in loses the stake.

• Betting window. Players place one or two bets. Most modern titles, Aviator included, allow two independent bets per round, which means two debits on your side.
• Flight. The multiplier rises on a curve. The player watches and chooses when to leave.
• Cash-out. Manual, or automatic at a target the player set in advance (for example 2.00x). Each cash-out is a separate credit.
• Crash. The round ends. Losing bets simply receive no credit; there is nothing else to process.

The house edge is not hidden in the curve; it is built into how often the round ends almost immediately. That is why the published RTP of crash titles tends to be higher than that of many slots: the maths is simple and the studio can show it plainly.

The titles operators ask for

Operators searching for an “Aviator API” or a “JetX API” usually want the whole genre, because players move between titles. These are the reference games of the category, as described by their studios:

• Aviator — Spribe. The title that defined the category. A red plane, two bets per round, live chat, visible bets of other players, and a published RTP of 97%. Its round results are provably fair.
• JetX — Smartsoft Gaming. A jet instead of a plane, and a denser interface with statistics of recent rounds. Smartsoft also builds JetX3 and a family of multiplier games around the same idea.
• Spaceman — Pragmatic Play. An astronaut, with a 50% cash-out option that lets the player bank half the stake and keep the rest flying.
• Balloon, Crash X, Big Bass Crash and similar. Studios keep reskinning the mechanic, because the mechanic is what players come back for.
• Chicken Road and step-based games. A close cousin: instead of a rising line, the player advances step by step and can stop at any step. We treat these alongside crash and instant titles.

Player habits differ by market. In India and Bangladesh, Aviator sits next to Andar Bahar and Teen Patti among the games players open first, and they like small stakes with fast repetition. In Latin America and Africa, crash games are frequently the first thing a mobile player opens. In Eastern Europe, JetX and its statistics panel have a loyal audience. A crash lobby that works across markets carries several titles, not one.

Provably fair, explained for operators

Provably fair means the round result is fixed before the round starts and can be checked afterwards. In Aviator, Spribe combines a server seed, whose hash is shown before the round, with seeds taken from the first players to bet; the combined value determines the crash point. After the round, the player can recompute it and confirm nobody changed it.

You do not have to implement anything for this. The verification lives inside the game. What you gain is a marketing argument: in markets where players distrust casinos, “you can check every round yourself” is worth putting in your lobby copy and your affiliate material.

Integrating crash games through one API

Crash titles use exactly the same integration as every other game in our catalogue. You call getGameList and filter on game_type: crash, our normalised category. The raw studio labels are inconsistent (many crash titles are labelled “slots” by their own studio), which is why we publish a normalised value and recommend building your crash tab on it.

1. Pull the catalogue with getGameList and keep the entries whose game_type is crash. Use instant as well if you want Mines, Plinko and similar in the same tab.
2. Create the player with createPlayer and the currency they play in.
3. Launch with getGame, passing device=mobile for phones. Load the URL in an iframe.
4. Answer our wallet callbacks: balance at session start, debit for each bet, credit for each cash-out.

Callbacks are GET requests carrying call_id, round_id and game_id, signed with md5(timestamp + salt_key). Your endpoint always answers HTTP 200 with the balance in minor units. The full contract is in the API documentation.

The wallet in a crash game: speed first

A crash round leaves no slack. The betting window is a few seconds long, and a player who taps “bet” expects the button to confirm immediately. Three practical points make the difference:

• Answer debits fast. Keep the debit handler lean: one balance check, one write, one response. Heavy fraud scoring can run afterwards.
• Expect parallel calls. Two bets from the same player in the same round arrive as two debits with the same round_id and different call_id. Lock per player, not per round.
• A loss has no credit. When the plane leaves without the player, no callback follows. Do not wait for a “zero win” to close the round in your reporting; rely on the round history.
• De-duplicate on call_id. A retried credit must return the original result, never pay twice.

Per-player round history is available with getPlayerHistory, which merges the legs of each round (debits, cash-outs, rollbacks) so support can answer “where is my cash-out?” in one lookup.

Currencies and micro-stakes

Crash players bet small and often, so the currency the game opens in matters. The session currency is set at launch and every callback carries it, with amounts in minor units. Native currencies on the catalogue include USD, EUR, INR, BDT, PKR, BRL, TRY, MXN, ARS, IDR, PHP, THB, VND, ZAR and ETB; for any other currency the account runs in USD or EUR and you convert on your side. Tell us which currencies you need at signup — the form asks for them.

The catalogue and the currency list change continuously; the current list is always the one returned by getGameList and getCurrencies.

Building a crash lobby that holds players

• Give the genre its own tab. Crash players do not browse slot grids. A dedicated “Crash” tab next to Slots and Live is standard now.
• Lead with two or three recognised titles, then the variants. Recognition drives the first click; variety drives the tenth session.
• Put the RTP and “provably fair” on the tile. It answers the first question before the player asks it.
• Pair crash with instant games. The same audience plays Mines and Plinko between crash rounds; see our instant games API page.
• Offer a demo. Many crash titles support getGameDemo, which lets affiliates and landing pages show the game without a deposit. Our free casino games API page explains demo mode.

Why operators add crash games through SoftAggregator

Crash is a genre where you want many studios under one contract. With SoftAggregator you get the crash vertical inside a catalogue of 40,000+ games from 200+ providers, one seamless wallet for everything, native local currencies, and onboarding that takes days rather than months. Operators already running slots with us switch on crash by filtering one field. The same catalogue feeds our game aggregator API for slots, table and instant games, and the live tables and game shows of our live casino offer.

Frequently asked questions

Explore more