Sitemap
Every page on this site — 49 of them — and the files written for machines rather than for browsers. Nothing here is behind a login.
Platform
What we supply, and who it is for.
- HomeWhat Casino Api Pro is, in one screen
- Game catalogueEvery game, with playable demos
- Wallet integrationYou keep the player balance
- Operator platformSessions, ledger, webhooks
- PricingPlans, limits and crypto payment
- FAQThe questions operators ask first
- Verify a roundCheck any outcome in your own browser
- Platform statusMeasured from your browser, right now
- ContactSupport, security, legal and privacy
- Get API keysSandbox credentials, instantly
Docs — Get started
- IntroductionWhat Casino Api Pro is, how the API is structured, and how money is represented.
- QuickstartFrom nothing to a playable sandbox session in six steps.
- AuthenticationCredential pairs, bearer tokens, the three token audiences, IP allowlisting and rotation.
- IdempotencyWhy every money endpoint is idempotent on your transaction_id, and how to write a retry loop that cannot double-debit.
- Rate limitsPer-plan throughput, the headers that report it, why a 503 is not a 429, and how to back off.
- ErrorsThe error envelope, status codes, the retryable flag, and how to handle failures well.
- Request IDs & logsThe X-Request-Id header, passing your own trace id through, and what to log.
- Test mode & live modeWhat differs between sandbox and production, and the checklist for going live.
Docs — Integrate
- Game catalogueListing the games enabled for your account, and what each field means.
- Sessions & launchCreating a session, opening the launch URL, session lifecycle, and closing early.
- Wallet integrationThe five calls we make to your wallet, every field on the wire, and the contract it must honour.
- TransactionsBet, win, refund and rollback; transaction states; and why the ledger is append-only.
- WebhooksEvents, payload shape, signature verification, the retry schedule, and the history you can pull.
- Rounds & historyYour rounds, movements, sessions, players and free bets — listed, for your servers.
- Reporting APITurnover, GGR, per-game performance and one player's position, for your own systems.
- Promotions and tournamentsFree bets, rain, cashback, referrals and tournaments — and why they all pay in free bets.
- Risk and chatFraud signals over your own data, and the moderated room your players talk in.
Docs — Reference
- Provably fairSeed commitment, the hash-to-float derivation, rotation and verification, and versioned mathematics.
- Game actionsThe launcher-side endpoints for every game: Mines, Magic Ball, Spin da’ Bottle, Under Over 7, Dice, Lucky Wheel, Nova Drop and Goal Jet.
- Run it from your own serversEverything 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 accountRoles, invitations, several businesses under one login, brands, tickets and setting your own RTP.
- Service levelWhat we commit to, how availability and response time are measured, and credits.
- Error codesEvery error code the API returns, its status, and whether retrying can help.
Games
Every game has a page with its return-to-player figure, volatility and stake range.
- Goal JetA shared flight every player watches at once. Cash out before it stops, or lose the stake.
- MinesA 5x5 board. Open safe tiles to climb the multiplier; one bomb ends the round.
- Spin da' BottleCall up or down, spin, and take 2x if the neck lands on your half.
- Magic BallThree cups, one ball. Cover a cup and take 2.9x if the ball is under it.
- DicePick a target and roll under it. Every target pays the same expected return, so the choice is volatility rather than value.
- Lucky WheelSixteen 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 7Two 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 DropA 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 the maths and the money actually work.
- All engineering notesThe index, newest first
- How a provably fair crash round is actually generatedA 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 doFive 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 checkRTP 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 yoursThe 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 callEvery 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.
Legal
For machines
Every documentation page, article and game is also published as Markdown: add .md to any of their URLs. These files index them, and all of them are generated from the same tables the pages themselves render from, so none can quietly stop being true.
- sitemap.xmlEvery indexable URL, with the date it last changed
- robots.txtCrawl permissions. Everything here is public
- llms.txtAn index of this site in Markdown, for assistants
- llms-full.txtThe whole site as one Markdown file
- docs/llms.txtThe API reference alone, without the marketing
- RSS feedNew engineering notes
- OpenAPI specGenerate a client from it