Spribe API integration
Review Spribe API integration through Aggregator with current catalogue categories, game-specific availability checks and safe launch recovery.
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
- 16
- 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
- Spribe
Source category breakdown
- Casino: 1 entries
- Crash: 1 entries
- flash: 11 entries
- Slot: 2 entries
- Slots: 1 entries
Labels are source metadata, not verified game capabilities.
Confirm the exact game, not only the brand
A Spribe catalogue listing is not evidence that any particular named title is enabled. Inspect the returned game list for the exact title and identifier needed by your product. Mixed category labels must not be interpreted as a promise that every game supports the same mode or integration feature.
Validate demo capability and production access separately. Keep the original launch request and idempotency key if a request times out; a new launch key cannot resolve an unknown result. Reconcile player funds and signed settlements before releasing a reservation or retrying a financial operation.
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.