Slot Machine Simulator API GET

Slot Machine Simulator is a tool for simulating slot machine spins with realistic reel symbols and payout calculations. It supports customizable number of reels, bet amounts, and multiple spins with detailed win/loss statistics.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/slotmachine

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Slot Machine Simulator response payload
  }
}

About the Slot Machine Simulator API

Slot Machine Simulator works by generating random reel results using weighted probabilities for different symbols, calculating payouts based on symbol matches and bet amounts, and tracking detailed statistics across multiple spins.

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

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

View all integrations →

Other ways to use Slot Machine Simulator

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit

Questions.

Common questions about the Slot Machine Simulator API.

Read the docs →

What does the Slot Machine Simulator API do?

How do I authenticate Slot Machine Simulator API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Slot Machine Simulator API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Slot Machine Simulator API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Slot Machine Simulator API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Slot Machine Simulator API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

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
`spins`Optional	integer	`5`	Number of spins to simulate default 1 · range 1-5
`reels`Optional	integer	`3`	Number of reels default 3 · range 3-5
`bet`Optional	number	`1`	Bet amount per spin default 1 · range 0-1000

Example request

1
2

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-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

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.

Sample response

{
  "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
`payout`Premium	number	`0`	Monetary payout amount won from spin
`win_type`Premium	string	`"none"`	Classification of win result for spin
`is_win`Premium	boolean	`false`	Whether spin resulted in winning combination
`total_bet`	number	`5`	Total amount wagered across all spins
`total_winnings`Premium	number	`0.5`	Total monetary winnings from all spins
`net_profit`Premium	number	`-4.5`	Calculated profit or loss after all spins
`wins`Premium	number	`1`	Count of successful winning spins
`losses`Premium	number	`4`	Count of losing spins in session
`win_percentage`Premium	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_multiplier`Premium	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 — 2 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	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

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.

Compare all pricing tiers →

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

1
2

curl "https://api.apiverve.com/v1/slotmachine" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/slotmachine-apiSource, issues and the examples this page is built from.ReferenceSlot Machine Simulator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/slotmachinenpm APIVerve.API.SlotMachineSimulatorNuGet

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.

Install — npm

npm install @apiverve/slotmachine

Node.js

const 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

npm@apiverve/slotmachineThe published Node.js client, versioned and signed.GitHubapiverve/slotmachine-apiSource, issues and the examples this page is built from.ReferenceSlot Machine Simulator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.SlotMachineSimulatorNuGet

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.

Python

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

@apiverve/slotmachinenpm APIVerve.API.SlotMachineSimulatorNuGet

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.

Install — NuGet

dotnet add package APIVerve.API.SlotMachineSimulator

C# / .NET

using 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

NuGetAPIVerve.API.SlotMachineSimulatorThe published C# / .NET client, versioned and signed.GitHubapiverve/slotmachine-apiSource, issues and the examples this page is built from.ReferenceSlot Machine Simulator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/slotmachinenpm

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

@apiverve/slotmachinenpm APIVerve.API.SlotMachineSimulatorNuGet

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.

PHP

$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

@apiverve/slotmachinenpm APIVerve.API.SlotMachineSimulatorNuGet

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.

Ruby

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.body

Resources

Also published for

@apiverve/slotmachinenpm APIVerve.API.SlotMachineSimulatorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Games

View all 21 →

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

Slot Machine Simulator API GET

Try it — live request, no key required

About the Slot Machine Simulator API

What people use it for

Ways to call it

Other ways to use Slot Machine Simulator

Questions.

Request parameters — GET /v1/slotmachine

Optional

Authentication

Response — GET /v1/slotmachine

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/slotmachine

Resources

Also published for

Call it from Node.js — GET /v1/slotmachine

Resources

Also published for

Call it from Python — GET /v1/slotmachine

Resources

Also published for

Call it from C# / .NET — GET /v1/slotmachine

Resources

Also published for

Call it from Go — GET /v1/slotmachine

Resources

Also published for

Call it from PHP — GET /v1/slotmachine

Resources

Also published for

Call it from Ruby — GET /v1/slotmachine

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Slot Machine Simulator API

Games

Related articles

Ready to build with Slot Machine Simulator? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog