Skip to content
LootBox Solutions

Integration models

There are two ways to put LootBox Solutions boxes in front of players. They are not mutually exclusive — most brands mix them (e.g. our recommended widget on the home page, handing off to the full iframe for play).

Model A — Embed the full iframe

Drop the LootBox Solutions player surface into your page as an <iframe>. LootBox Solutions renders the lobby, the box page, the open animation, the player’s inventory, and fulfillment. You provide a launch token and a wallet endpoint.

Your page  ─▶  <iframe src="https://{operator}.app.lootboxsolutions.com/play?token=…">
                 └─ lobby · box page · open · inventory · orders

Choose this when you want the fastest path to a complete, maintained experience and you’re happy for gameplay UI to live in our surface. You still control branding (colors, logo), language, currency, and which boxes are enabled.

Model B — Build your own surfaces

Use our APIs as a headless backend and render your own UI. Read the box catalog to build your own grid / lobby / “most popular” widget, and either:

  • hand off to the iframe for the actual open (mint a launch targeting a specific box), or
  • drive everything from your backend through the Server-to-server API — purchase, cashout, cancel, history — and render results yourself.
Your backend ─▶ GET /api/s2s/boxes            → build your own lobby/widget
Your backend ─▶ POST /api/s2s/launches        → hand a box to the iframe
        …or─▶ POST /api/s2s/purchase          → open boxes server-side

Choose this when you want full control of the player-facing UI, want boxes to live inside your own design system, or need server-to-server control of the gameplay lifecycle (e.g. for your own checkout, loyalty, or reconciliation).

A common shape, and the one the recommended widget is built for:

  1. Embed the recommended widget on your home page — a compact strip of popular boxes we render for you, chosen with the variant param (e.g. variant=popular&limit=8). It’s a small iframe over the catalog data, not a widget you build. (You can build your own from the catalog instead — that’s Model B.)
  2. A card action emits an event and your page navigates to that box’s page: a tap to browse and configure, or “Buy now” to launch with autoOpen so the box is purchased and opened as the page loads.
  3. The full iframe on the box page hosts the box, opening, and inventory.

What stays the same in both models

Regardless of model, these are always true:

  • You implement the wallet RPC and a webhook receiver.
  • Identity is playerExternalId; your wallet is authoritative.
  • Fairness, inventory, and fulfillment are handled by LootBox Solutions and surfaced through the same endpoints.

Next: Concepts & glossary.