Evolution API guide
Already decided on Evolution? This part explains how SSG connects you: the 27 APIs, the launch sequence, wallet rules, iframe requirements and a go-live checklist.
27APIs in 6 families
6step game launch
2settlement styles
10point go-live list
Authentication and launch, the One Wallet money flow, play modes, iframe rules, security and reporting, and the integration checklist, all in one place.
Open the full API guide ▾Close the API guide ▴
A · API mapTwenty-seven APIs, six jobs
Some APIs are enabled by default for new integrations; the rest are switched on with your account manager.
Player & launch
Create or log in a player, open a game session, return the launch address and embed games in an iframe.
- User Authentication
- Client API
- Iframe Integration
Transactions
Bets, wins, tips and promotions through One Wallet, plus cashier transfers, balance pushes and transaction look-ups.
- One Wallet
- eCashier
- Balance Push
- Wallet Transactions Status
Data & reporting
Game history, streaming of finished games, game rendering, jackpot banners, classification, currency rates and direct game launch for your own lobby.
- Direct Game Launch
- Game History
- Game Rendering
- Game Streaming
- Jackpot Banner
- Game Classification
- Currency Rates
- Chat Backoffice
Compliance
Unified reality check, checksums, application versions and reporting for Denmark, Portugal, Finland and North America.
- Checksum
- Unified Reality Check
- Denmark (Safe3)
- Portugal Safe
- Finland Reporting
- Application Version
- North America Reporting
Promotions
Reward Games campaigns and their event stream, real-time bonus notifications and player push notifications.
- Reward Games
- Reward Games Streaming
- Bonus
- Push Notification
Casino management
Create and configure casino instances.
B · Game launchFrom click to table in six steps
Player picks a table
After logging in on your site, the player opens a live game from your lobby.
Your server calls Evolution
A server-to-server POST over HTTPS sends the player, currency, language and game settings.
Evolution checks the wallet
The wallet confirms the player with your system. This step is skipped in Demo mode.
Game session is created
Evolution’s authentication service tells the gaming server that a session is coming and waits for it to be ready.
Launch address returns
Evolution answers with JSON holding the entry and location values for this session.
The table opens
Your server redirects the browser to that address and the live table loads with your custom parameters.
Server-to-server only
The authentication call is made by your server over HTTPS and never shown to the player. Use a domain name, and whitelist your server IPs first (IPv6 is not supported).
Rotating player hostnames
Optional. When on, the game address changes between requests and rotates one to four times a day for about 14 days. Always read it from the latest response.
Standard response codes
2xx means success, 4xx means a problem with your request, 5xx means an Evolution-side error.
C · Wallet & moneyOne Wallet: Evolution calls you, you answer fast
In One Wallet your system stays the single source of truth for balances. Evolution sends debit, credit and cancel requests to you and expects a clear status back every time.
Settlement style
Example: blackjack, 10 bet, the player splits a pair and wins both hands.
Mixed
One credit for every debit: two debits of 10, then credits of 20 and 20. Simplest to build, because each debit and its credit or cancel share a reference id.
Gamewise
One aggregated credit at the end of the game, however many debits there were: here 10, 10, then 40. Best when you need to know exactly when a round ended; once accepted, the round is closed to further credits.
What your reply means
SuccessThe operation completed. Also used for “bet already exists” and “already settled”, so repeated calls are safe.
RetryableSomething transient. The bet is rejected for now, the player stays in the game, and Evolution can retry the call.
FinalWill not be retried, but the session can be reused. For example insufficient funds: the player sees a short message and stays in the game.
FatalThe player session is closed immediately, for example with an invalid token. The player must log in and launch again.
Always answer HTTP 200 with a status and the request id, even for limit or lock rejections. A non-200 is treated as a technical failure.
If a call fails: retries
Online bets
Every 0.1 to 1 second while the bet can still join the round.
Offline retries
About 5 hours, every 1 to 10 minutes, in the background.
Promo payouts
About 72 hours on a separate policy.
Not retried: balance and user checks. Make every debit, credit, cancel and tip call idempotent using the transaction id, and link settlements to the original bet with its reference id.
Dealer tips
Tip debit, cancel and close follow the same idempotent rules. Full tipping support is mandatory for studios in the US and Canada.
eCashier
For moving money between your wallet and Evolution’s: check available balance, external credit and debit, player info and transaction status, over HTTPS with basic authentication and IP whitelisting.
Balance Push
Tell Evolution when a balance changes on your site. Include a timestamp so stale updates are dropped, batch roughly once per second, and never push changes caused by Evolution games. Slots and reward games are not supported.
D · Play modesFive ways to put a player at the table
DefaultReal money
The registered player plays with the balance held in your system.
MarketingReward Games
“Free money” vouchers with a separate balance and win cap. Winnings come back to you to pay out. One click switches the player to real money.
RegisteredPlay For Fun
Artificial currency for registered players, with an instant switch to real money.
PromoFun Bonus
Voucher play managed entirely on your side. Cannot convert to real money and launches directly to a table.
GuestsDemo
No registration needed, only language and currency. Direct launch only; the lobby is not allowed for security reasons.
E · Front-endEmbed it right the first time
16:9 on desktop
The iframe must keep a 16:9 ratio. No styles on html, body or the iframe that change its size.
Permissions up front
Fullscreen is required, plus clipboard access. Geolocation, Bluetooth and motion sensors are needed in some regulated markets. They must be in the tag; adding them by script does not work.
Avoid
No sandbox attribute, no iframe inside another iframe, and no iOS overflow:hidden on page or body.
Talk to the game
The Client API sends events such as application ready and lifecycle updates, and accepts commands such as stop autoplay or exit fullscreen. Useful for reality checks.
Smallest supported space for the game: 320×529 portrait, 568×320 landscape (CSS pixels), after your own header or footer. Tell the game your bar height when you embed it, or it will not scale correctly.
F · Security & reportingThe parts regulators and finance teams ask about
HTTPS only
Every call between Evolution and your servers is encrypted. Wrong keys or tokens are rejected.
Reports
Game history with bets, decisions, cards and outcomes; a streaming feed for finished games; classification of games and bets; currency rates; jackpot banner data.
Jurisdictions
Dedicated reporting for Denmark, Portugal, Finland and North America, plus checksum, unified reality check and application version APIs.
Keepalive
The game pings an address you choose at a fixed interval while the player is active, so you know when a session has ended. Live games only; RNG games do not support it.
G · Go-liveYour integration checklist
Decide three things before REST testing
Settlement style, whether players may have one or several sessions, and how you treat table ids (not depending on them is the recommended choice). Share these with your Technical Integration Manager.
- Whitelist your server IPs (IPv4 only; use domain names, not IPs, for endpoints)
- Build the authentication call and read the launch address from every response
- Implement One Wallet: debit, credit, cancel, balance and user check, all idempotent
- Return HTTP 200 with the exact status values for limits, locks and funds
- Handle retries safely: the same transaction id must always give the same answer
- Add dealer tips if you serve the US or Canada
- Embed with the correct iframe tag: 16:9, permissions in the tag, no sandbox, no nesting
- Run the Evolution Chrome integration check and fix any iframe issues it reports
- Wire up reporting and reconciliation, and the reality-check and country APIs that apply to you
- Certify with your account and integration managers; reward games and free rounds are agreed with your account manager
SSG Gaming
