PG Soft API integration

Plan PG Soft API integration with PGSoft catalogue records, currency-filtered game discovery, demo capability checks and wallet 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
170
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

  • PGSoft

Source category breakdown

  • Gamble Game: 1 entries
  • Slot: 3 entries
  • Slot Game: 50 entries
  • Slots: 116 entries

Labels are source metadata, not verified game capabilities.

Normalize categories without inventing capabilities

PGSoft records are displayed as PG Soft. The source catalogue may use several spellings for slot categories. Grouping those labels can help navigation, but does not establish that every entry has identical launch options, demo support or free-round capabilities.

Choose games from the current currency-filtered response and retain their exact identifiers. Validate demo support per entry before calling the demo endpoint. For production, test starting-balance reservation, signed settlement processing and return navigation for the specific games you intend to offer.

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.