Slot Machine API
Cymba is a hosted slot machine API for studios, operators, and platforms. Define your game in JSON, call the API, get back a complete spin result as multipliers. No engine to build or maintain.
API example
POST /api/v1/spin
Authorization: Bearer cy_live_...
{
"config": "classic-fruits",
"lines": 9,
"client_seed": "session-abc"
}
{
"result": {
"round_id": "01JQ7N2P...",
"grid": [[1,3,2],[2,3,4],[3,3,1]],
"summary": {
"total_multiplier": 15,
"breakdown": {
"payline": 15
}
},
"result_hash": "e7f2a1..."
},
"provably_fair": {
"server_seed_hash": "a3f1c8...",
"client_seed": "session-abc",
"nonce": 55
}
}
A slot machine API is a backend service your application calls to resolve a slot spin. Instead of implementing the random number generation, reel logic, win evaluation, and feature resolution yourself, you send a game definition and spin parameters to the API and receive the result.
Cymba is built for teams that want to ship slot-style games without building or maintaining a custom math engine. You define the game in JSON, store it in the dashboard, and call the API whenever your app needs a spin result.
A Cymba spin response includes the reel grid, symbol positions, win events broken down by line or mechanic, total multiplier, feature steps where applicable, and provably fair verification material.
It does not return a monetary payout. Cymba returns a multiplier; your platform decides what that multiplier is worth for a particular player and stake. That boundary keeps Cymba out of wallet, balance, and compliance concerns that are specific to each operator's market.
Everything about how a slot machine behaves lives in its config: reel strips, symbol weights, paytable, win mode, scatter rules, free-spin settings, feature mechanics, and max-win cap.
Cymba stores configs as JSON objects in the dashboard. Each config has a unique ID. When you call /api/v1/spin, you reference that ID. The same config is used for RTP calculation, PAR sheet export, and playground testing, so the math you test is the math that runs in production.
Cymba ships with template configs for common slot types. Classic three-reel and five-reel payline games, ways-to-win setups, scatter-triggered free spins, and cascading reel games are available as starting points.
You can clone a template, adjust the paytable and reels to match your game design, validate, and spin within minutes. No engine code needed for common mechanics.
Every Cymba API key comes with provably fair infrastructure. The server seed hash is committed before results are generated. Client seeds are accepted on every spin. After seed rotation, previous spins can be replayed and verified.
For platforms where player trust is a selling point, this is included rather than an add-on.
Cymba's free tier is available without a credit card. It gives full access to the dashboard, config editor, RTP tooling, PAR sheet exports, and the spin API under a test key.
Production API keys with higher rate limits are available on paid tiers. The free tier is designed for development and pre-launch testing, not as a usage cap for building the product.
Start with a free API key, clone a template, and run your first provably fair spin.