Simulate reel spins and track reel results across custom bets.
Slot Machine Simulator generates slot machine reel spins for configurable reels, bet sizes, and spin counts. Every run outputs symbol names and emoji for each reel; paid plans add payout calculations, win tracking, and net profit statistics.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"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
}
]
}
}
About the Slot Machine Simulator API
A slot machine simulator API for casino-style games, demos and probability lessons, with no real money involved. Each call spins three to five reels up to five times, drawing every symbol with weighted probabilities so cherries turn up often and sevens rarely. You choose the number of spins, the number of reels and the bet per spin, starting from zero.
The Free plan returns what lands on each reel for every spin, as an emoji and a name, with the bet, the total amount wagered and the list of eight symbols the machine uses. That is enough to animate the reels in a browser game, a Discord bot or a party app and decide outcomes your own way.
Paid plans add the payout side: the winnings for each spin, its win type and a win flag, plus session totals for winnings, net profit, wins, losses and win percentage, and the payout multiplier for every symbol. That turns the simulator into a ready-made backend for a slot game, or a quick way to show how a run of spins moves a player's balance over time.
How it works
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 whenever payout is above zero, so a small result counts toward wins although it returns less than the stake. 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.
What people use it for
- 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
Without writing code
The Slot Machine widget from WidgetSpark spins one on your desktop.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Slot Machine Simulator
Same data, same APIVerve account, same credit balance — one key works on all of them.
Which plan fits 25,000 spin simulations a month?
Are payout amounts and win percentages included on the Free plan?
Can I adjust the number of reels and the bet size?
Can I run multiple spins in a single request?
How does the simulator report losing spins?
Request parameters — GET /v1/slotmachine
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
spinsOptional | integer | 5 | Number of spins to simulate default 1 · range 1-5 |
reelsOptional | integer | 3 | Number of reels default 3 · range 3-5 |
betOptional | number | 1 | Bet amount per spin default 1 · range 0-1000 |
curl "https://api.apiverve.com/v1/slotmachine?spins=5&reels=3&bet=1" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
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.
Response — GET /v1/slotmachine
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"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 spin resulted in winning combination |
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 |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 1 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Slot Machine Simulator calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 200 | Free |
| Starter | $29.99 | 200,000 | 200,000 | $0.15 |
| Pro | $99.99 | 1,000,000 | 1,000,000 | $0.10 |
| Mega | $299.99 | 4,000,000 | 4,000,000 | $0.07 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/slotmachine
No SDK to install — this is a plain HTTPS call to /v1/slotmachine with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/slotmachine" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/slotmachine
Install the Node.js SDK, then call the Slot Machine Simulator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/slotmachineconst res = await fetch("https://api.apiverve.com/v1/slotmachine", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/slotmachine
No SDK to install — this is a plain HTTPS call to /v1/slotmachine with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/slotmachine",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/slotmachine
Install the C# / .NET SDK, then call the Slot Machine Simulator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.SlotMachineSimulatorusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/slotmachine");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/slotmachine
No SDK to install — this is a plain HTTPS call to /v1/slotmachine with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/slotmachine", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/slotmachine
No SDK to install — this is a plain HTTPS call to /v1/slotmachine with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/slotmachine");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/slotmachine
No SDK to install — this is a plain HTTPS call to /v1/slotmachine with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/slotmachine")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Slot Machine Simulator form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Slot Machine Simulator API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Slot Machine Simulator API.
Games
- Acrostic Puzzle Generator
- Anagram Puzzle Generator
- Card Deck Shuffler
- Coin Flipper
- Crossword Generator
- Cryptogram Generator
- Dice Roller
- Fill in the Blanks Generator
- Fortune Cookie Generator
- Game Character Generator
- Hangman Word Generator
- Lottery Number Generator
- Mad Libs Generator
- Maze Generator
- Rock Paper Scissors
- Slot Machine Simulator
- Spelling Bee Generator
- Superhero Name Generator
- Word Ladder Generator
- Word Scramble Generator
- Word Search Generator
Related articles
All articles →
Add Daily Horoscopes to Your App in 5 MinutesBuild a horoscope feature your users will actually check daily. Working code included.Read
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read
Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read