Developer Experience

Integrate a casino in an afternoon

One TypeScript SDK, zero runtime dependencies, one API host for sandbox and production. The integration is about 20 lines — and here they are.

$ npm install @slottylabs/sdk
launch-game.ts
import { SlottyClient } from '@slottylabs/sdk'; const slotty = new SlottyClient({ apiKey, webhookSecret }); const { launchToken } = await slotty.auth.createSSOToken({  playerId: 'your-player-id',  currency: 'EUR',  jurisdiction: 'MT',}); const url = slotty.games.getLaunchUrl('slotty-slots', launchToken);// → embed in an <iframe>. That's the integration.
The Whole Integration

No player migration. No URL config.

  • Seamless SSO — players are created on our side automatically at first launch, keyed to your player ID. No migration, no duplicate registration; your player database stays yours.
  • Un-forgeable launch tokens — single-use, 30-second, RS256-signed JWTs.
  • TypeScript-first — zero runtime dependencies, Node 18+, fully typed responses.
  • One API host for sandbox and production — the environment is derived from the API key, so go-live is one config change.
Events

Webhooks done right

7 event types today (round completed/cancelled, jackpot won, deposit confirmed, withdrawal completed/failed, player created), pushed to your server so you never poll. More on the roadmap.

Replay-proof signing

HMAC-SHA256 signatures with timestamp tolerance — a captured webhook cannot be replayed. The SDK verifies signatures for you.

Typed envelopes

Every event ships in a typed envelope with an idempotency ID — process each event exactly once, even across retries.

Delivery that survives outages

Exponential retries over 8 attempts, a circuit breaker, and a dead-letter queue with per-delivery replay from the admin panel. Your maintenance window doesn't lose events.

Sandbox

QA superpowers included

The sandbox runs the production stack in test mode — so what you test is what ships.

  • Arbitrary-balance test players — spin up a whale or a broke account in one call.
  • Forced game outcomes — make the next round win, lose, or trigger a feature, deterministically.
  • Webhook test events — fire any of the 7 live event types at your endpoint on demand.
  • Integration health endpoint — verify connectivity, auth, and webhook reachability in CI.
Observability

See every round, replay any round

Round event streams give you visibility into gameplay, and round reconstruction from persisted event logs enables dispute resolution — so support disputes end with evidence, not arguments.

The onboarding checklist (7 steps, from sandbox key to activation) is tracked in the platform and queryable by API — your project manager can watch go-live progress without asking anyone.

Get a sandbox key and start today

Docs are public, the SDK is on npm, and your sandbox tenant can be provisioned the same day you ask.

Read the Docs Get Your Sandbox Key