ghostaggDocs
PortalGet free API keys
Documentation

Build on ghostagg

Real provider slots behind one operator API, settled against your own wallet through signed callbacks.

Quickstart
Key to running game in five steps.
Wallet API
Five signed callbacks you implement.
API reference
Every endpoint, field and response.

ghostagg is a slot game aggregator with a remote game server. You run the casino — players, balances, payments. We run the games: maths, rounds, fairness proofs and the game clients. The two meet over two small APIs.

DirectionWhatAuth
You call usThe operator API: list the catalogue, mint a session for a playerAuthorization: Bearer mk_…
We call youThe wallet API: authenticate a session, debit a stake, credit a win, roll backHMAC-SHA256 signature

How a round flows

  1. Your lobby lists games from GET /operator/games.
  2. A player opens a game. Your server calls POST /operator/sessions with your own session token and a player reference. You get our sessionID and the launch parameters.
  3. You load the game client with those parameters. The client talks to our server; your token never reaches the browser.
  4. On load we call your wallet's authenticate. On every spin we call debit before the result is served, and credit when the round ends.
  5. Every round is recorded with its game version, seed and nonce before it is served, so any round can be proved afterwards.

Principles

  • Your money, your arithmetic. Amounts are opaque micro-units (1,000,000 = one currency unit). We never compute on them; for a win we send the multiplier and you compute the payout from the stake you recorded.
  • Idempotent by roundId. Every wallet call of a round carries the same roundId. A retry must return the settled result, never post twice.
  • Stake Engine compatible. The game-client API follows Stake Engine's paths, shapes and error codes, so existing clients run unchanged.
  • Provably fair. Each session commits to a server seed hash before the first round; the round record and the verifier make every result checkable.

Next

  • Quickstart: from API key to a running game in five steps.
  • Wallet API: the five callbacks your server implements.
  • API reference: every endpoint, field and response.
Next
Quickstart →