Skip to content

Getting started

Introduction

How the Flip Flap game server works with an aggregator or an operator: you launch sessions, we call your wallet.

What this is

The protocol of our own game server for Flip Flap, as the code behaves today and as our live tests check it. Pre-release: fields may still change before the first integration goes live.

Shape#

  1. 1One HTTPS host per environment (staging, production).
  2. 2You call us: create a session (launch), close it, read the catalog, read rounds and legs. These calls are signed and only accepted from your egress addresses.
  3. 3We call your wallet: bet, win, refund, balance, as signed JSON POSTs.
  4. 4The game runs in the player's browser from the launch URL, on our host only; it contacts no other origin and can be embedded in an iframe on any https: page.

Amounts on every money call are integers in minor units (cents for EUR and USD). Currencies: EUR, USD.

Base URL#

Provider API
https://<game-host>/provider/v1

A play, end to end#

  1. 1You POST /provider/v1/sessions and open the launch_url you get back for the player.
  2. 2The player presses play: we send a bet leg to your wallet for the stake times the mode's cost.
  3. 3The run plays in the client. When its animation ends, we send the win leg (also for 0) with round_final: true.
  4. 4You reconcile with GET /provider/v1/transactions or read a single round with GET /provider/v1/rounds/{round_id}.