Relax Gaming API integration

Assess Relax Gaming API integration using RelaxGaming catalogue records, explicit category limitations and workspace-specific game and currency access.

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
123
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

  • RelaxGaming

Source category breakdown

  • flash: 123 entries

Labels are source metadata, not verified game capabilities.

Treat legacy category labels as incomplete information

RelaxGaming is displayed as Relax Gaming. The source snapshot can classify records with a legacy label such as flash rather than a useful game category. That label alone proves neither a slot catalogue nor that a game requires Flash. Do not manufacture a supported-game-category list from the brand name.

Ask for clarification where catalogue metadata is insufficient for your filters or browser requirements. Confirm exact game identifiers, currencies and supported features through workspace discovery, then test the returned launch experience. The public brand listing does not confirm any wider distribution catalogue or partnership.

From catalogue discovery to wallet settlement

  1. Create a workspace and keep your X-API-Key on your backend. Confirm provider, game and currency enablement.
  2. Call getGameList for the intended play currency. Copy the returned identifier exactly; do not construct it from the brand or feed name.
  3. Test demo launches where supported. For production launches, reserve player funds and retain the request with its idempotency key.
  4. 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.