Testing

Staging Environment

All integration testing happens on the staging environment:

Track Availability

Not all tracks (game rounds) run continuously on staging. Some tracks are reserved for internal testing — including rollback scenarios and edge cases that require manual intervention.

To see which tracks are currently live, visit status.155.io and select Staging. If a track appears offline, this is intentional and not a bug.

Testing Your Integration

Step 1: Verify endpoints individually

Use the staging API to generate a game URL and open it in a browser. Walk through a full game round and verify that your server receives the expected callbacks:

1. /balance — called when the game loads
2. /bet — called when the player places a bet
3. /win — called when the round ends (amount 0 for a loss, > 0 for a win)
4. /rollback — called if a round is cancelled (refund the original bet)

Step 2: Verify balances

After each callback, confirm that the player's balance on your side matches what you return in the response. Common issues:

• Deducting the bet amount twice (not handling idempotent retries)
• Not crediting the win amount for freebet wins (isFree: true with amount > 0)
• Not refunding the bet on rollback

Step 3: Go-live readiness

Once you're confident your integration is working, contact our team to schedule a final verification. We will need:

• A staging URL and login credentials so we can access your platform
• We'll run a series of test rounds covering win, loss, and rollback scenarios
• We verify the callbacks against our internal logs to ensure everything matches

Fun Money Mode

You can test the game UI without implementing any endpoints by using fun money mode. Generate a game URL with currency: "XXX" and omit clientSessionId and clientPlayerId — no callbacks will be sent to your server.

See Game URL — Fun Money Mode for details.