Hacksaw Gaming API integration
Review Hacksaw Gaming API integration, regional feed grouping, current catalogue categories and workspace-specific launch and currency 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
- 822
- Catalogue feeds
- 3
- 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
- Hacksaw Asia
- Hacksaw Latam
- Hacksaw World
Source category breakdown
- flash: 141 entries
- InstantWin: 32 entries
- Slot: 474 entries
- Slots: 175 entries
Labels are source metadata, not verified game capabilities.
Keep regional game identifiers distinct
Hacksaw Asia, Latam and World feeds are grouped for discovery. Their counts must not be read as disjoint sets of unique titles. A game name found in several feeds is not sufficient to choose an API identifier: use the currency-filtered catalogue returned to your workspace.
Inspect each entry rather than treating the whole brand as a single game type. Slot, instant-win and legacy category labels can coexist in source data. Do not infer demo support or optional features from those labels; verify returned capabilities and test the selected identifier.
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.