Developer reference

API Documentation

WinClub operator integration · v1

Overview

This reference describes the WinClub operator API, not the upstream provider API. An operator account must be created by an administrator. Sign in to your operator account and open API & Docs for your agent code, AES key, MD5 key and wallet settings.

GET or POST
https://winclub26.live/api/public/v1/channelHandle

Keep all signing keys on your own server. Never embed them in browser code. Configure your wallet URL before testing bets and payouts.

Authentication

Send these four fields as query parameters for GET, or as a form-encoded or JSON body for POST. Encrypt the inner query string using your operator AES key.

agent     = YOUR_OPERATOR_AGENT_CODE
timestamp = current Unix time in milliseconds
param     = Base64(AES-128-ECB(PKCS7(inner_query), YOUR_AES_KEY))
key       = md5(agent + timestamp + YOUR_MD5_KEY)

Use lowercase hexadecimal for the MD5 signature.
URL-encode param when sending query parameters or form data.

These are placeholders, not credentials. Your personal keys are only available after signing in.

Game launch · s=0

The account is your external player ID: 1–40 letters, digits, underscores or hyphens. KindID identifies a game; 19001 is Rummy. Use the player's IP address.

Inner query before encryption:
s=0&account=player123&KindID=19001&ip=PLAYER_IP&lang=en_us

Successful response:
{
  "m": "/channelHandle",
  "s": 0,
  "d": { "code": 0, "account": "player123", "url": "GAME_LAUNCH_URL" }
}

Open the returned URL to launch the game. Test-server activity is billable; do not assume a launch is free demo play.

Game list · s=100

Inner query before encryption:
s=100

Response shape:
{
  "m": "/channelHandle",
  "s": 100,
  "d": {
    "code": 0,
    "games": [
      { "kindId": 19001, "name": "Rummy", "type": "Card", "icon": "GAME_ICON_URL" }
    ]
  }
}

The games array contains the available catalog. Use kindId as KindID when requesting a launch.

Wallet callbacks

WinClub sends GET requests to your configured wallet URL using the same four signed fields and your operator keys. The account is your external player ID. Verify the signature and decrypt param on your server before changing balances.

Operation   Meaning       Response d
1001        Balance       {code: 0, account, money}
1002        Bet / debit   {code: 0, account, money}
1003        Win / credit  {code: 0, account, money}
1004        Order status  {code: 0, status}
1005        Cancel order  {code: 0}

Response envelope:
{"m":"/channelHandle","s":1001,"d":{"code":0,"account":"player123","money":100}}

Transaction fields include: orderId, money, gameNo, kindId.
Insufficient balance: code 1.
Order statuses: 1 = OK, 2 = cancelled, 4 = not found.

Handle repeat transaction IDs without applying the same debit or credit twice. Callback retry schedules and delivery guarantees: NOT SPECIFIED IN PROVIDER DOCUMENTATION.

WinClub API error codes

These codes belong to the WinClub operator endpoint. Do not use them to interpret the provider's own responses.

CodeMeaning
0Success
5Invalid launch input
6Decryption failed
7Invalid signature or missing timestamp
8Unsupported operation
10Unknown operator agent
13Server or game launch error
32Operator suspended

GGR & account settings

GGR is bets minus wins. The configured operator percentage applies to positive GGR. Your percentage and recorded totals appear in your signed-in operator account; administrators manage percentages and account status.

Provider settlement timing and automatic balance deductions: NOT SPECIFIED IN PROVIDER DOCUMENTATION.

Open your account