API Docs

Game Integration API

Base URL: {API_BASE_URL}/v1/games

Authentication

Most endpoints require JWT via the Authorization header. Player game operations (info, start, play, end) identify sessions using merchantCode + playerId instead of JWT.

  • Authorization header: Bearer {JWT_TOKEN}
  • For player game endpoints, include merchantCode and playerId in the request body.
  • Content-Type: application/json

Game Types

Game TypeValueDescription
High-Lowhigh-lowCard comparison game where players guess if the next card will be higher, lower, or same
Coin Flipcoin-flipClassic coin flip game where players choose heads or tails

Endpoints: Games

POST/v1/games/info
Get Game Info

Sync and retrieve user information for the player.

POST/v1/games/start
Start Game

Initialize a new game session for a player.

POST/v1/games/play
Play Game

Play a round in the current game session.

POST/v1/games/end
End Game

End the current game session and finalize payouts.

Common Response Structures

{
  "success": true,
  "status": "SUCCESS",
  "message": "Human-readable message",
  "data": {},
  "timestamp": "2025-01-23T10:00:00.000Z"
}

Error Handling

Always check the success field in responses. Handle specific messages for better UX:

if (!response.success) {
  // Show error message to user
  showError(response.message);

  // Handle specific errors
  if (response.message.includes('Insufficient balance')) {
    // Redirect to deposit page
  }

  if (response.message.includes('session not found')) {
    // Restart game
  }
}

Game Flow