Signed launch URLs for real-money and demo play, in the player language and currency, on your own domain.
Request a demoCasino API
A casino API
your developers will finish.
Four wallet callbacks, signed requests, idempotent retries and documentation that answers the questions integrations actually break on. Most teams are live in under a week.
- 17,000+Games
- 4Wallet endpoints
- 3–7Days to integrate
- 24/7Technical support
What a casino API provider should give you
A casino API provider supplies game content and the technical layer that serves it: game launch, a seamless wallet that debits bets and credits wins against your own balance in real time, and the reporting that lets you reconcile both. The API is the product — the catalogue is only half of it.
Most integrations do not fail on the game list. They fail on the edge cases: what happens when your wallet times out mid-spin, whether a retried request can pay twice, how a round abandoned in the middle of a bonus feature gets settled, and what a void does to the balance that a refund does not. A provider that documents those clearly will cost you days. One that does not will cost you months and an unexplained ledger.
Ask for the documentation before you ask for a price. Ten minutes with it tells you more than six meetings: look for the signing scheme, the retry policy, idempotency, settlement of stranded rounds, and whether there is a real error code table rather than an invitation to contact support.
How it works
- CredentialsMerchant key, API secret and endpoints issued the same day, with sandbox access for your team.
- Wallet callbacksImplement balance, bet, win and rollback. Requests are HMAC-signed; every transaction carries a reference your side can make idempotent.
- Acceptance testLaunch, bet, win, free spin, rollback, disconnect mid-round and reporting — run against written criteria, by your team.
- ProductionCredentials switched, catalogue enabled per market, daily reconciliation report turned on.
What the API covers
Bet, win, rollback and balance — your ledger stays authoritative, ours reconciles to it every day.
Every transaction carries a unique reference. A repeated request returns the original result instead of creating a second one.
Grant, list and cancel campaigns from your own system, with the award settled into the same wallet.
Games, studios, categories, thumbnails and per-market availability, with incremental updates rather than a nightly dump.
Transaction-level records and aggregates by product, provider and game, exportable or pulled on a schedule.
Retrieve the full history of a disputed round, so support answers from the record rather than from a guess.
A separate integration guide per product, with reference implementations in Node and PHP.
Studios available through the API
One integration, the whole catalogue — enabled per market and per brand.
- and 150+ more
What it costs
Per product rather than one blended rate. The GGR definition is written into the contract and shown in a worked example on your own numbers.
No monthly platform fee, no minimum commitment, and no penalty for a slow month.
The full API documentation goes out before any commercial conversation, so your engineers can judge the integration themselves.
Frequently asked questions
What is a casino API?
A casino API is the interface through which an operator launches games and exchanges money events with a content provider. The core of it is the seamless wallet: the provider calls your system to debit a bet and credit a win against the player balance you hold, in real time.
How long does a casino API integration take?
For a team that already runs a platform, three to seven days is normal: implement four callbacks, test in the sandbox and switch credentials. Teams building from scratch should plan four to six weeks, mostly for licensing and payments rather than the API.
What happens if our wallet times out during a spin?
The request is retried. Because every transaction carries a unique reference and your implementation is idempotent, the retry returns the original result rather than paying twice. Rounds abandoned mid-feature are settled by a sweeper that writes only the outcome the game has finalised.
Can we get the API documentation before signing?
Yes. We send the full integration guide as a PDF on request, before any commercial conversation — a partner who reads it and walks away was never going to be a good fit.
Do you support demo play?
Yes. Demo launches run without wallet calls and without a player account, which makes them suitable for acquisition pages, review sites and affiliate traffic.
Also worth reading
- Casino API Cost per Month: What Operators Actually PayA line-by-line cost model for a casino games API: setup fee, monthly minimum, GGR share by product, studio minimums, payment costs and the operational work nobody quotes.
- Seamless Wallet vs Transfer Wallet: What Changes for the OperatorHow seamless and transfer wallet integrations differ in balance integrity, timeout handling, idempotency, stranded rounds, reconciliation and player experience.
- Aggregator vs Direct Integration: Making the Content DecisionComparing a games aggregator with direct studio integrations: integration and maintenance cost, commercial rate, configuration control, reporting, dependency risk and how to run a hybrid model.
Read the documentation first
Tell us which products you need and we will send the integration guides and a sandbox account the same working day. Commercial terms after your engineers have had a look, not before.