Callisto Games

One API. Multiple game providers.

B2B game aggregation for operators and platforms. Connect once for game catalogue, launches, seamless wallet callbacks, reconciliation and content operations across multiple providers.

Request access View Developer Docs

Existing customer? Sign in to the Operator Portal

POST/v1/sessionsOperator API

X-Agg-Key-Id:     ak_5f2c…
X-Agg-Timestamp:  1792224000
X-Agg-Signature:  HMAC-SHA256(…)

{
  "game_id":        "0f3c8a2e-…",
  "player_id":      "p_48213",
  "currency":       "EUR",
  "player_country": "MT"
}

→ 201 Created
{ "session_id": "2c7e…", "launch_url": "https://…" }

POST{wallet_url}Wallet callback

{ "action": "bet", "transaction_id": "t-8f21",
  "round_id": "r-77", "currency": "EUR", "amount": "1.50" }

← 200 { "balance": "98.50", "transaction_id": "op-4471" }

Built for operator integrations

Signed API
Seamless wallet
Sandbox & test suite
Reconciliation
Operator Portal

How it works

Integrate once. Keep your own platform and wallet.

Your backend connects to Callisto Games for catalogue, game sessions and reconciliation. Providers connect behind the Callisto Games technical layer, and every bet and win reaches your wallet in one format.

Your backend reads the catalogue: GET /v1/games.
It opens a session: POST /v1/sessions returns a launch_url.
The player's browser opens the game at launch_url.
Gameplay runs between the game client and the provider.
The provider reports bets, wins and rollbacks to the Callisto Games gateway.
Callisto Games calls your wallet at wallet_url in one format.
Your wallet answers with the balance after the movement.
You reconcile by transaction and round: GET /v1/transactions, /v1/rounds.

How an operator integrates with Callisto Games. The operator never integrates a provider directly.

See the integration model

Capabilities

Aggregation beyond the catalogue

Everything an operator needs after the first launch, behind one signed API.

Catalogue & metadata

Games, providers, studios, images and types in one normalized model.

GET /v1/games

Real-money and demo sessions

One call opens a game; demo needs no player and no wallet.

POST /v1/sessions

Wallet bet / win / rollback

One callback contract for every provider, idempotent by transaction.

POST {wallet_url}

Free spins

Grant and cancel free rounds through one API where the provider supports them.

POST /v1/free-spins

Jackpots & live data

Jackpot values and live tables as providers report them, where supported.

GET /v1/jackpots

Geo restrictions

Country rules returned in the catalogue and enforced at launch.

GET /v1/games?country=

Transactions & rounds

Look up any movement or round by its identifier.

GET /v1/rounds/{id}

Invoice webhook

Issued and voided invoices posted to your endpoint, signed like a wallet call.

invoice.issued

Explore technology

Provider network

Content through one integration

Direct provider integrations and selected upstream content sources, delivered through one connection. Availability depends on market, licence and commercial terms.

Evoplay

Mancala Gaming

Live Vegas

Abcdabra

Jacktop

EvenBet

Explore providers

Operator Portal

Your integration workspace

Credentials, wallet configuration, validation, catalogue and assets, documentation shortcuts and team access in one operator-facing workspace.

Operator Portal

portal

API keys, sandbox and production
Wallet URL and configuration
Wallet validation suite
Catalogue and game assets
Documentation shortcuts
Team access

Developer experience

Built for integration teams

The guide your engineers work from, from the first signed request to the go-live checklist.

Quick Start

From a sandbox key to a first game session.

HMAC authentication

Signing rules, code samples, test vectors and a signature tester.

OpenAPI & Postman

The contract as OpenAPI JSON/YAML and a ready Postman collection.

Wallet test suite

Run it from the portal or from your CI against your wallet.

Go-live checklist

What has to pass before production keys are issued.

Errors & retries

Every error code and whether to retry it, documented once.

Developer Docs

Reconciliation

Support does not stop at launch

Look up transactions and rounds by identifier, understand wallet movements and reconcile operational issues without provider-specific formats.

Explore technology

For providers

Distribute through Callisto Games

Providers integrate once into the Callisto Games network, pass staging and testing, onboard their catalogue and become available to enabled operators.

Become a provider

FAQ

Questions operators ask first

Is Callisto Games an aggregator, or does it connect to one?

Callisto Games is the aggregator. Provider connectivity, the game gateway and the wallet contract are ours; operators connect to Callisto Games once.

Do we keep our own platform and wallet?

Yes. Your backend calls the Operator API, and Callisto Games calls your wallet for every bet, win and rollback in one format. Player balances never leave your platform.

Can we connect our own providers into Callisto Games?

No. Provider integrations are built and run by Callisto Games. If you already hold a direct commercial agreement with a provider, its terms can be used where agreed, while the technical connection still runs through Callisto Games.

Is every game available in every country?

No. Availability depends on market, licence and commercial terms. Restrictions are returned in the catalogue and enforced at launch, so your lobby can hide what a player may not open.

How do we test before production?

You start with sandbox credentials, a signature tester and a wallet validation suite. Production access and production hostnames are issued during go-live onboarding.

Add content in one integration

Tell us your markets, currencies and platform setup. We will show the integration path and available content.

Request access Developer Docs