Overview
Casino API integration is a set of interfaces for connecting games, wallet and events to the platform. RakeCore’s casino API integration includes REST and WebSocket, idempotent seamless wallet callbacks and a NATS event bus for reliable integration.
The casino game API is built around a seamless wallet: the game accesses the player balance through callbacks, and idempotency guarantees a repeated request does not cause a double charge. Through a single API you get access to games, bets and transactions without separate protocols per module.
Events are published to NATS on subject channels — wallet.*, game.*, bonus.*, withdrawal.* — so you can subscribe to the streams you need in real time. Sandbox, auth and idempotency simplify building and testing the integration before production.
Step by step
Get keys and set up authentication for REST and WebSocket connections to the API.
Test the integration in a sandbox environment with test games, wallet and events.
Implement idempotent wallet callbacks so a repeated request does not cause double charges.
Subscribe to wallet.*, game.*, bonus.* and withdrawal.* channels for real-time processing.
Switch from sandbox to live keys and push the integration to production.
What you get
- REST and WebSocket interfaces
- Authentication and access key management
- Idempotent seamless wallet callbacks
- Events on NATS: wallet.*, game.*, bonus.*, withdrawal.*
- Sandbox environment for testing
- Documentation and request idempotency
Benefits
REST and WebSocket give access to games, wallet and events through one interface.
Idempotent seamless callbacks prevent double charges on request retries.
The NATS bus publishes wallet.*, game.*, bonus.* and withdrawal.* for reactive processing.
Sandbox, auth and documentation speed up integration before production.
Powered by these modules
Frequently asked questions
Which protocols does the casino API support?
REST for requests and WebSocket for real-time connections, plus a NATS event bus for asynchronous integration and subscriptions.
What is a seamless wallet in the API?
A model where the game accesses the player balance on the platform via real-time callbacks rather than holding the balance itself.
Why is idempotency needed?
Idempotency guarantees that resending the same request (e.g. on a network failure) does not cause a double charge or credit.
Which events are published?
Events go on NATS subject channels: wallet.* for the wallet, game.* for games, bonus.* for bonuses and withdrawal.* for withdrawals.
Is there a sandbox?
Yes. The sandbox environment lets you test games, wallet and events with test data before connecting live keys.
How does authentication work?
Access is issued via keys with auth for REST and WebSocket. Live and test keys are separated between sandbox and production.
Can I subscribe to only the events I need?
Yes. NATS channels are subject-based, so you can subscribe to, for example, only withdrawal.* or wallet.* without extra traffic.
Is the API suitable for in-house games?
Yes. Through the casino game API you can connect both third-party and your own games using the same seamless wallet and events.