Response simulator | 155.io API Docs

Validate your wallet's callback responses against the 155 contract — entirely in your browser. Pick a callback, paste the JSON your wallet returns, and the linter flags anything that would break the integration. The Explorer shows the exact response to return for each scenario.

This checks the response body (status, required fields, idempotency). Remember the transport rule: every callback must respond with HTTP 200 — the outcome lives in status. See Error codes.

Response linter

Callback

Paste your wallet's response and lint it

Explorer — what to return per scenario

Accepted

{
  "status": "SUCCESS",
  "requestId": "abc-123",
  "clientPlayerId": "player-1",
  "balance": 900000,
  "currency": "USD"
}

Insufficient funds

{
  "status": "INSUFFICIENT_BALANCE_ERROR",
  "requestId": "abc-123",
  "clientPlayerId": "player-1",
  "balance": 500,
  "currency": "USD"
}

Duplicate (replay)

{
  "status": "DUPLICATE_TRANSACTION_ERROR",
  "requestId": "abc-123",
  "clientPlayerId": "player-1",
  "balance": 900000,
  "currency": "USD"
}

Bet limit

{
  "status": "BET_LIMIT_REACHED_ERROR",
  "requestId": "abc-123",
  "clientPlayerId": "player-1",
  "balance": 1000000,
  "currency": "USD"
}

Free-bet problem

{
  "status": "BONUS_ERROR",
  "requestId": "abc-123",
  "clientPlayerId": "player-1",
  "balance": 1000000,
  "currency": "USD"
}

See the per-callback contracts: /balance · /bet · /win · /rollback.