Evolution API integration
Evaluate Evolution API integration through Aggregator using current live and regional catalogue records, launch requirements and settlement guidance.
This guide describes access through Aggregator, not a direct provider API or an official partnership. Catalogue visibility does not confirm production entitlement, provider endorsement or permission to operate in any territory.
Current catalogue records
- Catalogue entries
- 579
- Catalogue feeds
- 2
- Snapshot updated
Counts describe cached catalogue records, not guaranteed unique games. Regional feeds may overlap. Refreshes can change the figures; use workspace discovery for actual access.
Source feed names
- Evolution Live
- Evolution Live (Asia)
Source category breakdown
- Casino Live: 59 entries
- CasinoLive: 210 entries
- Live: 301 entries
- Lobby: 9 entries
Labels are source metadata, not verified game capabilities.
Distinguish lobbies from individual entries
Evolution is presented as one brand across its live catalogue feeds. When reviewing the category breakdown, distinguish lobby records from individual game records rather than assuming every entry is a separate table. The catalogue response, not the brand display name, supplies the identifier for a launch.
Confirm which feed and currency are enabled for your workspace. Test the actual returned launch URL and player return flow on your target devices; public category labels do not establish table limits, schedules, languages or market permissions. Request those details for the intended games.
From catalogue discovery to wallet settlement
- Create a workspace and keep your X-API-Key on your backend. Confirm provider, game and currency enablement.
- Call getGameList for the intended play currency. Copy the returned identifier exactly; do not construct it from the brand or feed name.
- Test demo launches where supported. For production launches, reserve player funds and retain the request with its idempotency key.
- Validate signed settlement callbacks, duplicate handling and unknown outcomes before completing the production checklist.
Currency, territory and commercial access
The public snapshot does not establish supported currencies or territories for your account. Confirm these with the team and your workspace entitlements. A regional feed name is not regulatory approval. Provider and game restrictions still apply after activation.
Compare activation plans and estimate GGR fees. Activation, player balances and GGR funding are separate; estimates are not invoices or currency conversions.