Skip to main content

​
1. Basic Information

  1. This document consists of Wallet-API and Game-API.
    • Wallet-API is the API requested from the vendor to modify player balances, implemented by the vendor.
    • Game-API is the API for vendors to obtain game-related data from the game.
  2. POST and PUT requests support application/json and application/x-www-form-urlencoded; GET request parameters are passed via query string.
  3. All API connection timeout is 2 seconds, and read timeout is 15 seconds.
  4. Online credit operations for players in this game are integrated with proxy bettor. Dealer information is recorded as on-site accounting proposals, and the proposal ID associated with each bet is provided when synchronizing bet records.
  5. This game offers a 1-to-1 traditional proxy bettor mode (hereinafter referred to as “Traditional Mode”) and a 1-to-many quick proxy bettor mode (hereinafter referred to as “Quick Mode”).
  6. Integrators must provide separate player wallets for both Traditional Mode and Quick Mode to ensure a complete gaming experience. In the following documentation, these will be referred to as “Traditional Wallet” and “Regular Wallet” respectively.
  7. Integrators should note the following settings to ensure a complete gaming experience:
    • Enable touch controls
    • Enable localStorage
    • Enable webview-related settings (such as GestureDetector and other gesture-related operations)
    • Avoid overwriting any inline styles

​
2. Amount Description

For parameters related to amount, integers do not need decimal points, e.g., 100. Since on-site chip betting uses whole number amounts, all amount-related values will only be integers.

​
3. Authentication Method

All API requests must include a key parameter for verification. The calculation method is: 
key = md5(parameter combination + platform secret key)
Please refer to individual API descriptions for the specific parameter combinations.