Instant games API: Plinko, Mines, Dice and HiLo for your lobby

What are instant games, and what does an instant games API do?

Instant games are one-screen casino games where a single decision produces a result in about a second: drop a ball in Plinko, open a tile in Mines, roll a number in Dice, guess higher or lower in HiLo. An instant games API gives your casino the list of these titles, a launch link for each, and a wallet callback for every stake and every payout. With SoftAggregator they come from the same catalogue and the same contract as slots, live tables and crash.

The category grew out of crypto casinos, where players wanted simple games with visible maths and verifiable results. It has since become a standard tab in mainstream lobbies, because the same players who like crash games want something to do between rounds, and because instant games convert well on small phone screens.

The five mechanics behind almost every instant game

Studios release dozens of instant titles each year, but nearly all of them are variations of five mechanics. Knowing them helps you build a tab that feels varied instead of repetitive.

• Plinko. A ball falls through a pyramid of pegs and lands in a slot with a multiplier. The player chooses the number of rows (commonly 8 to 16) and a risk level. Low risk clusters the multipliers around 1x; high risk puts large multipliers on the edges and small ones in the middle.
• Mines. A 5×5 grid hides gems and mines. The player picks how many mines are on the board, then reveals tiles one by one; every safe tile raises the multiplier, and the player may cash out at any moment. More mines means a steeper curve.
• Dice. The player sets a target number and bets that the roll lands over or under it. The payout follows directly from the chosen probability, so a 50% chance pays a little under 2x and a 10% chance pays a little under 10x.
• HiLo. A card is shown; the player bets whether the next one is higher or lower, chaining guesses to build a multiplier, or skipping a card they do not like.
• Instant keno and limbo. Pick numbers and see the draw at once, or choose a target multiplier and win if the random result reaches it. Limbo is essentially a crash round without the flight.

Step games such as Chicken Road belong to the same family: the player moves forward one step at a time and decides when to stop. See our Chicken Road page, and the Mines and Plinko game pages for title-level detail.

Studios that shaped the category

Instant games are a studio-driven genre, and a good tab mixes several of them. Operators most often ask for:

• Spribe Turbo Games — the collection that sits next to Aviator: Mines, Plinko, Dice, HiLo, Keno, Goal, Mini Roulette and Hotline. Spribe publishes a 97% RTP across these titles and makes them provably fair.
• BGaming — one of the first studios to bring Plinko and Dice from crypto casinos into regular lobbies, with clean interfaces and adjustable risk.
• Hacksaw Gaming — known for scratch cards and quick-play mini games that sit between instant and slot, with a strong mobile design.
• Turbo-style collections from Evoplay, JILI and others — often lighter graphics and very fast rounds, popular in Asian and Latin American lobbies.

The value of an aggregated catalogue here is that you are not locked into one studio’s look. Players get bored of a single visual style faster in instant games than in slots, where the themes vary by design.

Provably fair: why it matters more here than anywhere else

Provably fair means each result is derived from a server seed committed in advance (the player sees its hash before betting), a client seed the player can change, and a nonce that counts the bets. After the bet, the server seed is revealed and anyone can recompute the result. The player does not need to trust the casino; they can check.

In instant games the result is the whole game, so this transparency is the product. Crypto-native players look for the fairness button before they deposit. Nothing is required from your side: the verification screen is inside the game. Put “provably fair” on the tile and in your lobby filters, and you answer the audience’s first objection.

What your wallet sees from an instant game

Instant games are the highest-frequency traffic your wallet will handle. A player on Dice with auto-bet can place several bets per second. The integration itself is the standard one — POST methods to our API, GET callbacks to your endpoint — but the load profile is different from slots.

• One debit, one credit, per bet. A Dice roll or a Plinko ball is a round of its own. A losing bet usually produces only the debit.
• Multi-step rounds in Mines and HiLo. The stake is debited when the round opens; the credit arrives only when the player cashes out. Between the two, the player may take many seconds. Do not time out the round on your side.
• Auto-bet bursts. Size your callback endpoint for bursts, not averages. Keep the handler short and move analytics to a queue.
• Idempotency on call_id. Under load, retries happen. The same call_id must return the original answer.

Every callback is a GET request signed with md5(timestamp + salt_key), amounts are integers in minor units, and the reply is always HTTP 200 with error 0, 1 or 2 in the body. The method-by-method reference is in our API documentation.

Building the instant tab from the game list

Our getGameList response carries a normalised game_type. Instant titles carry instant; crash titles carry crash. Studios label these games inconsistently in their own feeds, so filtering on our field instead of the studio label is what keeps Plinko from hiding among the slots.

1. Filter game_type on instant (and crash if you run one combined “Originals” or “Fast games” tab).
2. Group by mechanic using the game name: a “Plinko” row, a “Mines” row, a “Dice” row. Players look for the mechanic, not the studio.
3. Create players with the currency they deposit in, and launch with device=mobile on phones.
4. Offer the demo where play_for_fun_supported is true: instant games are easy to understand after three free tries.

The same list powers your whole lobby through the casino game aggregator API, so an instant tab is a filter, not a new project.

Stakes, currencies and the micro-bet audience

Instant players stake small. That makes local currencies important: a bet of 10 rupees or 20 taka should look like 10 rupees or 20 taka, not a converted dollar amount. Currencies with native support include INR, BDT, PKR, BRL, MXN, ARS, TRY, IDR, VND, THB, PHP, MYR, KRW, JPY, EUR, USD and GBP among others. Where a currency is not native, the account runs in USD or EUR and you convert for the player; ask us about yours.

Also look at the upper end. High-rollers do play Dice and Mines, and the per-bet win cap set by the studio decides how far they can go. Read it in the rules of the version you launch before designing a VIP promotion around an instant title.

Why add instant games through SoftAggregator

You get the instant vertical from many studios alongside 40,000+ games and 200+ providers, all under one contract and one seamless wallet that also covers slots, crash and live casino content. Onboarding is quick, the documentation is public, and the support team answers on Telegram and e-mail. If crash is your next step, the crash games API page covers Aviator, JetX and the multiplier genre.

Frequently asked questions

Explore more