# Casino Api Pro

> A REST API that supplies provably fair casino games to licensed gaming operators. The operator keeps the players, the wallet, the KYC and the licence; we run the games, the sessions, the round state machine and the settlement ledger.

Casino Api Pro is casino game infrastructure for operators. One integration gives an operator a catalogue of crash, mines, dice and instant games, with sessions, rounds, settlement and webhooks.

Facts that are checkable rather than claimed:

- **The operator holds the balances.** Every bet and win is an HTTP call from us to the operator’s own wallet API. We never hold player funds.
- **Every round is verifiable.** Outcomes come from a commit-reveal scheme; the server seed is committed before the round and revealed after, and anyone can recompute the result at https://casinoapipro.com/verify without an account.
- **The return-to-player figure of every game is published** on its catalogue page, along with its volatility and stake limits.
- **Sandbox keys are issued on signup**, with play money and every game enabled. No sales call, no minimum volume, and the documentation is public whether or not you sign up.
- **Money is decimal strings, never floats.** `"10.50"` is valid and `10.5` is rejected.
- **Writes are idempotent.** The operator mints the `transaction_id` and it is the idempotency key for the movement.

## Start here

- [Casino Api Pro](https://casinoapipro.com/): One REST integration for provably fair casino games. Crash, mines, dice and instant games with sessions, rounds and settlement. Free sandbox keys instantly — no sales call, no minimum volume.
- [Casino games](https://casinoapipro.com/games): Every game on Casino Api Pro: crash, mines, dice and instant games. Provably fair, one REST integration, free demo play in your browser. See RTP, stake ranges and rules.
- [Wallet integration](https://casinoapipro.com/wallet): Casino Api Pro never holds player funds. Every bet and win is a call to your existing wallet API. Four operations, an idempotency contract, and a reference wallet you can test against.
- [Operator platform](https://casinoapipro.com/features): What you get with the integration: one REST API for the whole catalogue, multi-tenant isolation, signed sessions, an append-only ledger, signed webhooks and a free sandbox that behaves like production.
- [Pricing](https://casinoapipro.com/pricing): A platform fee plus a share of game revenue. Sandbox is free forever. Paid plans unlock live play, paid in crypto. No card required, no minimum volume, no exclusivity.
- [Sitemap](https://casinoapipro.com/sitemap): Every page on casinoapipro.com in one place: the API documentation, the game catalogue, the engineering notes, and the machine-readable files an assistant can read directly.
- [FAQ](https://casinoapipro.com/faq): Licences, integration time, the free plan, wallet guarantees, timeouts, crypto payment, multi-tenancy and support — answered plainly.
- [Verify a round yourself](https://casinoapipro.com/verify): Check any round's outcome in your own browser. No request reaches our servers — paste the seeds and watch the result fall out of them.
- [Contact](https://casinoapipro.com/contact): Support, security, legal and privacy addresses for Casino Api Pro, and a form if you would rather we came to you. Support at support@casinoapipro.com.
- [Platform status](https://casinoapipro.com/status): Live status for the Casino Api Pro API, game launcher, assets and documentation — measured from your own browser, right now.
- [Get free API keys](https://casinoapipro.com/signup): Create a Casino Api Pro account and get sandbox API credentials instantly. No sales call, no approval queue, no minimum volume. Every game enabled, play-money wallet included.

## API documentation

- [Introduction](https://casinoapipro.com/docs/introduction.md): What Casino Api Pro is, how the API is structured, and how money is represented.
- [Quickstart](https://casinoapipro.com/docs/quickstart.md): From nothing to a playable sandbox session in six steps.
- [Authentication](https://casinoapipro.com/docs/authentication.md): Credential pairs, bearer tokens, the three token audiences, IP allowlisting and rotation.
- [Idempotency](https://casinoapipro.com/docs/idempotency.md): Why every money endpoint is idempotent on your transaction_id, and how to write a retry loop that cannot double-debit.
- [Rate limits](https://casinoapipro.com/docs/rate-limits.md): Per-plan throughput, the headers that report it, why a 503 is not a 429, and how to back off.
- [Errors](https://casinoapipro.com/docs/errors.md): The error envelope, status codes, the retryable flag, and how to handle failures well.
- [Request IDs & logs](https://casinoapipro.com/docs/request-ids.md): The X-Request-Id header, passing your own trace id through, and what to log.
- [Test mode & live mode](https://casinoapipro.com/docs/test-and-live.md): What differs between sandbox and production, and the checklist for going live.
- [Game catalogue](https://casinoapipro.com/docs/catalogue.md): Listing the games enabled for your account, and what each field means.
- [Sessions & launch](https://casinoapipro.com/docs/sessions.md): Creating a session, opening the launch URL, session lifecycle, and closing early.
- [Wallet integration](https://casinoapipro.com/docs/wallet.md): The five calls we make to your wallet, every field on the wire, and the contract it must honour.
- [Transactions](https://casinoapipro.com/docs/transactions.md): Bet, win, refund and rollback; transaction states; and why the ledger is append-only.
- [Webhooks](https://casinoapipro.com/docs/webhooks.md): Events, payload shape, signature verification, the retry schedule, and the history you can pull.
- [Provably fair](https://casinoapipro.com/docs/provably-fair.md): Seed commitment, the hash-to-float derivation, rotation and verification, and versioned mathematics.
- [Game actions](https://casinoapipro.com/docs/game-actions.md): The launcher-side endpoints for every game: Mines, Magic Ball, Spin da’ Bottle, Under Over 7, Dice, Lucky Wheel, Nova Drop and Goal Jet.
- [Rounds & history](https://casinoapipro.com/docs/history.md): Your rounds, movements, sessions, players and free bets — listed, for your servers.
- [Reporting API](https://casinoapipro.com/docs/reports.md): Turnover, GGR, per-game performance and one player's position, for your own systems.
- [Promotions and tournaments](https://casinoapipro.com/docs/engagement.md): Free bets, rain, cashback, referrals and tournaments — and why they all pay in free bets.
- [Risk and chat](https://casinoapipro.com/docs/risk-and-chat.md): Fraud signals over your own data, and the moderated room your players talk in.
- [Run it from your own servers](https://casinoapipro.com/docs/automation.md): Everything the console can do, driven by an API key: catalogue, tournaments, promotions, risk, chat, the operational record, currencies and support — and the four things that deliberately stay behind a person.
- [Team and account](https://casinoapipro.com/docs/account.md): Roles, invitations, several businesses under one login, brands, tickets and setting your own RTP.
- [Service level](https://casinoapipro.com/docs/service-level.md): What we commit to, how availability and response time are measured, and credits.
- [Error codes](https://casinoapipro.com/docs/error-codes.md): Every error code the API returns, its status, and whether retrying can help.
- [OpenAPI specification](https://api.casinoapipro.com/openapi.json): The machine-readable spec for every endpoint, served from the live API.

## Games

- [Goal Jet](https://casinoapipro.com/games/goal-jet.md): Crash. RTP 97.00%. high volatility. A shared flight every player watches at once. Cash out before it stops, or lose the stake.
- [Mines](https://casinoapipro.com/games/mines.md): Instant. RTP 97.00%. variable volatility. A 5x5 board. Open safe tiles to climb the multiplier; one bomb ends the round.
- [Spin da' Bottle](https://casinoapipro.com/games/spin-bottle.md): Instant. RTP 95.56%. low volatility. Call up or down, spin, and take 2x if the neck lands on your half.
- [Magic Ball](https://casinoapipro.com/games/magic-ball.md): Instant. RTP 96.67%. medium volatility. Three cups, one ball. Cover a cup and take 2.9x if the ball is under it.
- [Dice](https://casinoapipro.com/games/dice.md): Instant. RTP 97.00%. player-chosen volatility. Pick a target and roll under it. Every target pays the same expected return, so the choice is volatility rather than value.
- [Lucky Wheel](https://casinoapipro.com/games/lucky-wheel.md): Instant. RTP 97.00%. high volatility. Sixteen prizes, one spin, from 0.2x back to 150x. The faces are equal and the odds are not, so every chance is published on the paytable.
- [Under Over 7](https://casinoapipro.com/games/under-over-7.md): Instant. RTP 96.67%. player-chosen volatility. Two dice, one call: under seven, exactly seven, or over. Every option returns the same, so the seven is rarer and larger rather than a worse bet.
- [Nova Drop](https://casinoapipro.com/games/nova-drop.md): Instant. RTP 97.01%. high volatility. A ball falls through eight rows of pegs into one of nine slots. The odds are not a setting — they are Pascal’s triangle, and the corners pay 29x because only one path in 256 reaches them.

## Engineering notes

- [How a provably fair crash round is actually generated](https://casinoapipro.com/blog/provably-fair-crash-explained.md): A crash multiplier is derived from a hash of a server seed the operator committed to before the round, combined with a client seed the player controls. Publish the commitment first and anyone can check afterwards that the result was not chosen.
- [What a casino wallet integration actually has to do](https://casinoapipro.com/blog/wallet-integration-what-it-actually-requires.md): Five endpoints: balance, debit, credit, refund and rollback. The only hard requirement is that debit and credit are idempotent on the transaction id you are given — everything else is detail.
- [RTP, house edge and the number operators should actually check](https://casinoapipro.com/blog/rtp-house-edge-honestly.md): RTP is the long-run share of stakes returned to players; the house edge is what is left. The number worth checking is not the advertised RTP but whether the running game reproduces it — which requires the operator to be able to see their own round history.
- [Idempotency in a betting API, and why the key is yours](https://casinoapipro.com/blog/idempotency-in-betting-apis.md): The safest design gives the caller the idempotency key rather than generating one. If you mint the transaction id, a retry after a timeout is unambiguous — and a timeout is the one failure every integration eventually meets.
- [Why we publish prices and hand out keys without a sales call](https://casinoapipro.com/blog/self-serve-versus-sales-call.md): Every aggregator in this market asks you to book a demo before seeing anything. We publish the prices, the limits and the documentation, and issue sandbox keys instantly — because an integrator can evaluate an API far better than a salesperson can describe it.

## Optional

- [Terms of Service](https://casinoapipro.com/terms): The agreement between Casino Api Pro and the operators who use our casino game API: what we provide, what you are responsible for, acceptable use, fees, liability and termination.
- [Privacy Policy](https://casinoapipro.com/privacy): What Casino Api Pro collects, what it deliberately never receives, who else touches it, and how long it is kept. No analytics, no advertising trackers, no player personal data.

## Notes for whoever is reading this

- Every link above ends in `.md` and returns Markdown. Drop the `.md` for the HTML page.
- Documentation only, as one file: https://casinoapipro.com/docs/llms.txt
- Everything on this site, as one file: https://casinoapipro.com/llms-full.txt
- The API's machine-readable spec: https://api.casinoapipro.com/openapi.json
- Nothing here is behind a login, and none of it is generated on request.