Overview
Each reel is filled independently by a weighted draw from eight symbols. The weights, out of 108, are Cherry 30, Lemon 25, Orange 20, Grape 15, Bell 8, Star 5, Diamond 3 and Seven 2, so a Cherry lands on about 28% of reels and a Seven on under 2%. Payout multipliers rise as symbols get rarer: 2, 3, 5, 10, 20, 50, 100 and 200.
Matches count from the leftmost reel only. The simulator counts how many reels in a row, starting at reel one, show the same symbol as reel one; the same symbol further along after a break does not count. If every reel matches, `win_type` is `jackpot` and `payout` is multiplier x bet x number of reels. If three or more match but not all, which needs four or five reels, `win_type` is `match` and `payout` is multiplier x bet x matched count x 0.5. Exactly two leading matches give `small`, paying half the bet for any symbol. Anything else is `none` with a payout of 0.
`is_win` is true only when `payout` is more than the bet, so a `small` result, which returns half the stake, counts as a loss in `wins`, `losses` and `win_percentage` while its payout still counts toward `total_winnings`. `total_bet` is spins x bet, `net_profit` is total winnings minus total bet, and `win_percentage` is wins divided by spins, times 100. Money values are rounded to two decimals.
`spins` accepts 1-5, `reels` 3-5 and `bet` 0-1000. A bet of 0 is honoured and gives zero payouts. On the Free plan `payout`, `win_type`, `is_win`, the winnings, profit and win/loss totals, and each symbol's `payout_multiplier` are null.
Live Test Slot Machine Simulator API →
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/slotmachine?spins=5&reels=3&bet=1" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/slotmachine?spins=5&reels=3&bet=1', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/slotmachine?spins=5&reels=3&bet=1",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/slotmachine?spins=5&reels=3&bet=1", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
spinsOptional | integer | Number of spins to simulate default 1 · range 1–5 |
reelsOptional | integer | Number of reels default 3 · range 3–5 |
betOptional | number | Bet amount per spin, rounded to 2 decimal places default 1 · range 0–1000 |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"total_spins": 5,
"num_reels": 3,
"bet_per_spin": 1,
"spins": [
{
"spin_number": 1,
"reels": [
{
"symbol": "🍋",
"name": "Lemon"
},
{
"symbol": "🍒",
"name": "Cherry"
},
{
"symbol": "🍒",
"name": "Cherry"
}
],
"bet": 1,
"payout": 0,
"win_type": "none",
"is_win": false
},
{
"spin_number": 2,
"reels": [
{
"symbol": "⭐",
"name": "Star"
},
{
"symbol": "🍋",
"name": "Lemon"
},
{
"symbol": "⭐",
"name": "Star"
}
],
"bet": 1,
"payout": 0,
"win_type": "none",
"is_win": false
},
{
"spin_number": 3,
"reels": [
{
"symbol": "🍊",
"name": "Orange"
},
{
"symbol": "🍇",
"name": "Grape"
},
{
"symbol": "🍋",
"name": "Lemon"
}
],
"bet": 1,
"payout": 0,
"win_type": "none",
"is_win": false
},
{
"spin_number": 4,
"reels": [
{
"symbol": "🍒",
"name": "Cherry"
},
{
"symbol": "⭐",
"name": "Star"
},
{
"symbol": "🔔",
"name": "Bell"
}
],
"bet": 1,
"payout": 0,
"win_type": "none",
"is_win": false
},
{
"spin_number": 5,
"reels": [
{
"symbol": "🍒",
"name": "Cherry"
},
{
"symbol": "🍒",
"name": "Cherry"
},
{
"symbol": "7️⃣",
"name": "Seven"
}
],
"bet": 1,
"payout": 0.5,
"win_type": "small",
"is_win": true
}
],
"total_bet": 5,
"total_winnings": 0.5,
"net_profit": -4.5,
"wins": 1,
"losses": 4,
"win_percentage": 20,
"available_symbols": [
{
"symbol": "🍒",
"name": "Cherry",
"payout_multiplier": 2
},
{
"symbol": "🍋",
"name": "Lemon",
"payout_multiplier": 3
},
{
"symbol": "🍊",
"name": "Orange",
"payout_multiplier": 5
},
{
"symbol": "🍇",
"name": "Grape",
"payout_multiplier": 10
},
{
"symbol": "🔔",
"name": "Bell",
"payout_multiplier": 20
},
{
"symbol": "⭐",
"name": "Star",
"payout_multiplier": 50
},
{
"symbol": "💎",
"name": "Diamond",
"payout_multiplier": 100
},
{
"symbol": "7️⃣",
"name": "Seven",
"payout_multiplier": 200
}
]
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
total_spins | number | 5 | Total number of spins simulated in session |
num_reels | number | 3 | Number of reels used per spin |
bet_per_spin | number | 1 | Bet amount placed per individual spin |
spins | array[5] | Array containing detailed information for each spin | |
spin_number | number | 1 | Sequential number identifying this spin |
reels | array[3] | Array of reel results for this spin | |
symbol | string | "🍋" | Emoji symbol displayed on the reel |
name | string | "Lemon" | Human-readable name of reel symbol |
bet | number | 1 | Bet amount wagered for this spin |
payoutPremium | number | 0 | Monetary payout amount won from spin |
win_typePremium | string | "none" | Classification of win result for spin |
is_winPremium | boolean | false | Whether the spin paid more than the bet (a small half-stake return is not a win) |
total_bet | number | 5 | Total amount wagered across all spins |
total_winningsPremium | number | 0.5 | Total monetary winnings from all spins |
net_profitPremium | number | -4.5 | Calculated profit or loss after all spins |
winsPremium | number | 1 | Count of successful winning spins |
lossesPremium | number | 4 | Count of losing spins in session |
win_percentagePremium | number | 20 | Percentage of spins that resulted in wins |
available_symbols | array[8] | Array of all possible symbols used | |
symbol | string | "🍒" | Emoji symbol available in slot machine |
name | string | "Cherry" | Name of the available symbol |
payout_multiplierPremium | number | 2 | Payout multiplier for symbol matches |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- Game Development
- Implement slot machine mechanics in casino games and gambling applications
- Probability Analysis
- Analyze slot machine probabilities and expected values for educational purposes
- Entertainment
- Provide safe, simulated slot machine experience without real money gambling
- Testing
- Test slot machine algorithms and payout structures for game design and balancing
Other ways to use Slot Machine Simulator
Set up Slot Machine Simulator on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Games: