Ezugi API integration
Prepare Ezugi API integration through Aggregator with live catalogue category details, game selection checks and signed settlement requirements.
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
- 101
- Catalogue feeds
- 1
- 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
- Ezugi
Source category breakdown
- Casino Live: 1 entries
- CasinoLive: 11 entries
- flash: 58 entries
- Live: 28 entries
- marbles: 2 entries
- Roulette: 1 entries
Labels are source metadata, not verified game capabilities.
Review mixed live and legacy metadata
Ezugi catalogue records can combine live-game categories, roulette and other or legacy labels. Use the detailed breakdown below to identify what needs review instead of classifying every record as an individual live table. Category names do not define table limits or operating schedules.
Confirm the desired game and currency in your workspace response. Review player return URLs and wallet settlement for the actual selected entries, including duplicate and out-of-order events. Agree market permissions and any game-specific operational requirements before moving from demo testing to production.
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.