API Doc

Protocol

HTTP(s) are used to send and receive data. Data of type JSON is supported. Refer to the (http://www.json.org/)for more information of JSON.

In additional to the standard HTTP protocol, the following HTTP Headers are required:

Please use UTF-8 as the default encoding for all encode/ decode codes when convert text to/ from byte[].

Following codes shows thats way of using MD5:

public staticString digest(byte[] input) {
		byte[] digest = Digest.md5().compute( input );
		return Hex.encodeHexString( digest );
	}

Glossary

1. Game Provider: e-games development team
2. Merchant: The party that wants to integrate e-games to their website
3. API Requestor :The party responsible for calling the function
4. API provider: The party responsible for hosting the function
5. Acct ID: Player’s unique identity code

API Interface Definition

Game Lobby Page

Usage: Player enters Game Lobby Page after clicking provider's button found in merchant website.

Interface Name：Redirect To Game Lobby

API Provider：Game Provider

API Requestor：Merchant

1. For language, Refer to Appendix-2.
2. Kindly refer 4.15 Domain List to get the latest domain for replacing the sampledomain.
3. For DEMO may replace it with your merchant code.

Game Lobby Redirect URL and Parameters:

https://lobby.sampledomain.com/DEMO/auth/?acctId=TESTPLAYER1&language=zh_CN&token=fe1a85adc54545d2963b661a22d09c9e&channel=Web&isLobby=true

Game Page

Usage: Player enters E-games page by clicking Goto Game or Real Money button found in merchant website.

Interface Name：Redirect To Game

API Provider：Game Provider

API Requestor：Merchant

1. For language, Refer to Appendix-2.
2. For game, Refer to appendix 4."Appendix 4".
3. Kindly refer 4.15 Domain List to get the latest domain for replacing the sampledomain.
4. For DEMO may replace it with your merchant code.

Game Redirect URL and Parameters(real money):

https://lobby.sampledomain.com/DEMO/auth/?acctId=TESTPLAYER1&language=zh_CN&token=fe1a85adc54545d2963b661a22d09c9e&game=sLongX3

Game Redirect URL and Parameters(play for fun):

https://play.sampledomain.com/game?merchantCode=DEMO&game=sLongX3&language=zh_CN

User Authorization

Usage： Merchant will provide this request for Game provider to authenticate the session.

Interface Name： authorize

API Provider： Merchant

API Requestor： Game Provider

Request Message Definition for AuthorizeRequest：

Response message definition for AuthorizeResponse：

AcctInfo type definition:

Note :

1. Refer to appendix 3 for a list of currency code that system support."Appendix 3".
2. Refer to appendix 4 for a list of cryptocurrency code that system support."Appendix 4".
3. Please skip the “balance” for the Authorize Response(Set to 0).
4. Acct ID format: [a-zA-Z0-9_-@]{1,50}. Example: TestPlayer_1

Authorize (Request and response messages example)

JSON AuthorizeRequest:

{
		"acctId": "TESTPLAYER1", 
		"language": "en_US", 
		"merchantCode": "TEST", 
		"gameCode": "sLongX3", 
		"forFun": "false", 
		"token": "fe1a85adc54545d2963b661a22d09c9e", 
		"serialNo": "20120722224255982841"
	}

JSON AuthorizeResponse:

{
		"acctInfo": {
			"acctId": "TESTPLAYER1", 
			"balance": 0, 
			"userName": "TestPlayer", 
			"currency": "CNY"
			"siteId": "SITE_CNY1"
		},									
		"merchantCode": "TEST",
		"msg": "success",
		"code": 0,
		"serialNo": "20120722224255982841"
	}

Example in Http client:

Query user information

Usage Scenario: Search for user information (Balance etc).

Interface Name： getAcctInfo

API Provider： Game Provider

API Requestor： Merchant

Request Message Definition for GetAcctInfoRequest：

Response message definition for GetAcctInfoResponse：

AcctInfo type definition:

GetAcctInfo (Request and response messages example) :

JSON GetAcctInfoRequest:

{
		"acctId": "TESTPLAYER1", 
		"merchantCode": "TEST", 
		"serialNo": "20120802152140143938"
	}

JSON GetAcctInfoResponse:

{
		"list": [{
			"userName": "TestPlayer1", 
			"currency": "CNY", 
			"acctId": "TESTPLAYER1", 
			"balance": 1000,
			"isOnline": 0
		}],										
		"resultCount": 1,
		"pageCount": 1,
		"merchantCode": "TEST",
		"msg": "success",
		"code": 0,
		"serialNo": "20120802152140143938"
	}

Example in Http client:

Query user balance (One Wallet)

Usage Scenario : Search for user balance.

Interface Name ： getBalance

API Provider ： Merchant

API Requestor ： Game Provider

Request Message Definition for GetBalanceRequest：

Response message definition for GetBalanceResponse：

GetBalance (Request and response messages example) :

JSON GetBalanceRequest：:

{
		"acctId": "TESTPLAYER1", 
		"token": "fe1a85adc54545d2963b661a22d09c9e", (For Staging Only)
		"merchantCode": "TEST", 
		"serialNo": "20120802152140143938",
		"currency": "CNY"
	}

JSON GetBalanceResponse:

{
		"acctInfo": {
			"userName": "TestPlayer1", 
			"currency": "CNY", 
			"acctId": "TESTPLAYER1", 
			"balance": 1000
		},										
		"merchantCode": "TEST",
		"msg": "success",
		"code": 0,
		"serialNo": "20120802152140143938"
	}

Transfer (One Wallet)

Usage Scenario ：

1. When player place bet, Game Provider will send the transfer request to merchant, and merchant will deduct the player balance.
2. When Game Provider payout, Game Provider will send the transfer request to merchant, and merchant will increase the player balance.
3. If the player lose the bet, Game Provider will send a transfer request stated payout = 0.

Interface Name ： transfer

API Provider ： Merchant

API Requestor ： Game Provider

Request Message Definition for TransferRequest：

SpecialGame type definition:

**specialGame only will pass during type = 4, payout**

Note:

1. If the transfer Id received is duplicated, merchant need to check the transfer status and reply the status to Game Provider. CANNOT process the transfer with same transfer id.
2. If the transfer Id are duplicated or not found, Merchant should return us Error Code: 109. Except this error code, provider will continue resend you the reference Id.
1. Check if transfer Id exist (for all type)
2. Check if place bet transaction (reference Id) of this transaction exists or not (for type 2 and type 4 only)
3. Check if place bet transaction (reference Id) of this transaction has another cancel bet or payout transaction (for type 2 or type 4 only)

Response message definition for TransferResponse:

Transfer (Request and response messages example):

JSON TransferRequest:

{
		"acctId": "TESTPLAYER1", 
		"transferId": "0ab9bdca06c14811b24653468e60988", 
		"currency": "USD", 
		"amount": 10, 
		"type": 4, 
		"ticketId": "234950357", 
		"channel": "Web", 
		"gameCode": "sLongX3", 
		"merchantCode": "TEST", 
		"serialNo": "20120722231413699735",
		"referenceId": "dfffdca06c14811b24653468e60", 
		"mainBetId": "1ab9bdca06c14811b24653468e60988",  (For Staging Only)
		"token": "fe1a85adc54545d2963b661a22d09c9e",  (For Staging Only)
		"specialGame": {
			"type": "Free", 
			"count": 10, 
			"sequence": 1 
		}	
	
	}

JSON TransferResponse:

{
		"transferId": "0ab9bdca06c14811b24653468e609838", 
		"merchantCode": "TEST", 
		"merchantTxId": "20130813014319279367", 
		"acctId": "TestPlayer1", 
		"balance": "1050", 
		"msg": "success", 
		"code": 0, 
		"serialNo": "20120722231413699735"
	}

Transfer Jackpot (Request and response messages example):

JSON TransferRequest:

{
		"acctId": "TESTPLAYER1", 
		"transferId": "0ab9bdca06c14811b24653468e60988", 
		"currency": "USD", 
		"amount": 10, 
		"type": 6, 
		"ticketId": "234950357", 
		"channel": "Web", 
		"gameCode": "sRoma", 
		"merchantCode": "TEST", 
		"serialNo": "20210917171413632534"
		"referenceId": "dfffdca06c14811b24653468e60", 
	
	}

JSON TransferResponse:

{
		"transferId": "0ab9bdca06c14811b24653468e60988", 
		"merchantCode": "TEST", 
		"merchantTxId": "20210917014319279367", 
		"acctId": "TestPlayer1", 
		"balance": "1250", 
		"msg": "success", 
		"code": 0, 
		"serialNo": "20210917171413632534"
	}

Transfer History (One Wallet)

Usage Scenario ：

1. Search for transfer history.

Interface Name ： transferHistory

API Provider ： Game Provider

API Requestor ： Merchant

Request Message Definition for TransferHistoryRequest：

Response message definition for TransferHistoryResponse:

TransferInfo definition:

TransferHistory (Request and response messages example):

JSON TransferHistoryRequest:

{
		"beginDate": "20120721T175139", 
		"endDate": "20120723T174139", 
		"pageIndex": 1, 
		"merchantCode": "TEST" 
	}

JSON TransferHistoryResponse:

{
		"list": [{ 
			"transferId": "667706462", 
			"acctId": "TEST10001", 
			"ticketId": "749084635", 
			"type": 1, 
			"amount": 20, 
			"transferTime": "20130908T151100", 
			"gameCode": "sLongX3", 
			"status": 0, 
			"channel": "Web", 
		}], 
		"resultCount": 1, 
		"pageCount": 1, 
		"merchantCode": "TEST", 
		"code": 0, 
		"msg": "success", 
		"serialNo": "20120726214956563472" 
	}

TransferHistory Jackpot (Request and response messages example):

JSON TransferHistoryRequest:

{
		"beginDate": "20210917T175139", 
		"endDate": "20210920T174139", 
		"pageIndex": 1, 
		"merchantCode": "TEST" 
	}

JSON TransferHistoryResponse:

{
		"list": [{ 
			"transferId": "667706462", 
			"acctId": "TEST10001", 
			"ticketId": "749084635", 
			"type": 6, 
			"amount": 1250, 
			"transferTime": "20210918T151100", 
			"gameCode": "sRoma", 
			"status": 0, 
			"channel": "Web", 
		}], 
		"resultCount": 1, 
		"pageCount": 1, 
		"merchantCode": "TEST", 
		"code": 0, 
		"msg": "success", 
		"serialNo": "20210917171413632534" 
	}

Deposit (Balance Transfer)

Usage Scenario ：When merchant wishes to transfer money to Game provider wallet for a particular member.

Interface Name： deposit

API Provider： Game Provider

API Requestor： Merchant

Request Message Definition for DepositRequest：

Response message definition for DepositResponse:

Note:

1. Serial No is the identity of the message, and one Serial No for one request or response. Please make sure the Serial No is unique for deposit and withdraw message.
2. We advise to use GUID (UUID), or the date+time+random string as the Serial No
3. Acct ID format: [a-zA-Z0-9_-@]{1,50}. Example: TestPlayer_1

Deposit (Request and response messages example):

JSON DepositRequest:

{
		"acctId": "TESTPLAYER1", 
		"amount": 200, 
		"currency": "CNY", 
		"merchantCode": "TEST", 
		"serialNo": "20120722231413699735"
	}

JSON DepositResponse:

{
		"newPlayer": false, 
		"beforeBalance": 1000.0000, 
		"afterBalance": 1500.0000, 
		"transactionId": "500648408", 		
		"merchantCode": "TEST", 
		"msg": "success", 
		"code": 0, 
		"serialNo": "20120722231413699735"
	}

Example in Http client:

Withdrawal

Usage Scenario： When merchant wishes to transfer money from Game provider wallet for a particular member.

Interface Name： withdraw

API Provider： Game Provider

API Requestor： Merchant

Request Message Definition for WithdrawRequest：

Response message definition for WithdrawResponse：

Note:

1. Serial No is the identity of the message, and one Serial No for one request or response. Please make sure the Serial No is unique for deposit and withdraw message
2. We advise to use GUID (UUID), or the date+time+random string as the Serial No.
3. Acct ID format: [a-zA-Z0-9_-@]{1,50}. Example: TestPlayer_1

Withdraw (Request and response messages example):

JSON WithdrawRequest:

{
		"acctId": "TESTPLAYER1", 
		"amount": 200, 
		"currency": "CNY", 
		"merchantCode": "TEST", 
		"serialNo": "20120722231413699735"
	}

JSON WithdrawResponse:

{
		"newPlayer": false, 
		"beforeBalance": 1500.0000, 
		"afterBalance": 1000.0000, 
		"transactionId": "500648408", 
		"merchantCode": "TEST", 
		"msg": "success", 
		"code": 0, 
		"serialNo": "20120722231413699735"
	}

Example in Http client:

Check Transfer

Usage Scenario ：

1. Search for transfer history.

Interface Name ： checkTransfer

API Provider ： Game Provider

API Requestor ： Merchant

Request Message Definition for CheckTransferRequest：

Response message definition for CheckTransferResponse:

CheckTransfer (Request and response messages example):

JSON CheckTransferRequest:

{
		"merchantCode": "TEST", 
		"serialNo": "2020012004074" 
	}

JSON CheckTransferResponse:

{
		"status": 1, 
		"currency": "PTS", 
		"acctId": "TESTPLAYER1@TEST", 
		"valueBefore": 199992.000000, 
		"valueChange": "1000.000000", 
		"valueAfter": 200992.000000, 
		"merchantCode": "TEST", 
		"code": 0, 
		"msg": "Success", 
		"serialNo": "2020012004074" 
	}

Example in Http client:

Query Player Betting History

Usage Scenario： Search for bet history

Interface Name： getBetHistory

API Provider： Game Provider

API Requestor： Merchant

Request Message Definition for GetBetHistoryRequest：

Response message definition for GetBetHistoryResponse:

BetInfo definition：

More details Please refer to appendix-4"Appendix-4".

GetBetHistory (Request and response messages example):

JSON GetBetHistoryRequest:

{
		"beginDate": "20120721T175139", 
		"endDate": "20120723T174139", 
		"pageIndex": 1, 
		"merchantCode": "TEST", 
		"serialNo": "20120723175139440637"
	}

JSON GetBetHistoryResponse:

{
		"list": [{
			"ticketId": 633161396, 
			"acctId": "Test10001", 
			"categoryId": "SM", 
			"gameCode": "sLongX3", 
			"ticketTime": "20130908T161044", 
			"betIp": "8.8.8.8", 
			"betAmount": 20, 
			"winLoss": 30, 
			"currency": "CNY", 
			"result": "23412", 
			"jackpotAmount": 1.5, 
			"luckyDrawId": 0, 
			"completed": True, 
			"roundId": 1879, 
			"sequence": 0, 
			"channel": web, 
			"balance": 234.000000, 
			"jpWin": -100.000000
			"referenceId": ""
			"isCascade": true
			"isBuyFeature": false
		}], 
		"resultCount": 1, 
		"pageCount": 1, 
		"merchantCode": "TEST", 
		"msg": "success", 
		"code": 0, 
		"serialNo": "20120723175139440637"
	}

JSON Jackpot GetBetHistoryResponse:

{
			"channel": Web, 
			"result": "{\"ticketId\":\"31\",\"jpCategory\":\"1\",\"jpCode\":\"Roma\"}", 
			"currency": "XXX", 
			"acctId": "TestPlayer488", 
			"balance": 20000024.4, 
			"jpWin": 0.0, 
			"gameCode": "sRoma", 
			"sequence": 0, 
			"referenceId": "", 
			"ticketId": 35, 
			"categoryId":"SM", 
			"luckyDrawId": 0, 
			"roundId": 0, 
			"betAmount": 0.0, 
			"completed": true, 
			"jackpotAmount": 0.0, 
			"ticketTime": "20221103T160952", 
			"betIp": "xxx.xxx.xxx.xxx"
	}

Example in Http client:

Query Bet Detail

Usage: Merchant may use the link to generate bet details without logon in BO.

Interface Name： Query Bet Detail

API Provider：Game Provider

Direct link for query bet detail:

https://gameapi.backoffice-domain.com/betDetails?merchantId=MERCHANT_CODE&token=MD5_HASH&lang=en&ticketId=TICKET_ID

1. For secretKey, merchant may request from support agent.
2. Use MD5 hash "ticketId|secretKey" for the token parameter.

Force Logout for Online Members

Usage Scenario： Kick selected user or all users out of E-games

Interface Name： kickAcct

API Provider： Game Provider

API Requestor： Merchant

Request Message Definition for KickAcctRequest：

Response message definition for KickAcctResponse：

KickAcct (Request and response messages example):

JSON KickAcctRequest:

	{
		"acctId": "Test10001", 
		"merchantCode": "TEST", 
		"serialNo": "20130430164644935780"
	}
	

JSON KickAcctResponse:

{
		"list": ["Test10001"], 
		"merchantCode": "TEST", 
		"code": 0, 
		"msg": "success", 
		"serialNo": "20130430164644935780"
	}

Example in Http client:

Retrieve Game List

Usage Scenario: Provide a list of available games with details

Interface Name: getGames

API Provider: Game Provider

API Requestor: Merchant

Request Message Definition of GetGamesRequest:

Response message definition for GetGamesResponse:

Game type definition:

GetGames (Request and response messages example):

JSON GetGamesRequest:

{
		"merchantCode": "TEST", 
		"serialNo": "20130430164644935780"
	}

JSON GetGamesResponse:

{
		"games": [{
			"gameCode": "sLongX3", 
			"gameName": "Long Long Long", 
			"cnName": "龙龙龙", 
			"line": 1, 
			"category": "SM"
		}]
	}

Example in Http client:

Retrieve Domain List

Usage Scenario: Provide a list of available domains

Interface Name: getDomainList

API Provider: Game Provider

API Requestor: Merchant

Request Message Definition of GetDomainListRequest:

Response message definition for GetDomainListResponse:

GetDomainList (Request and response messages example):

JSON GetDomainListRequest:

{
		"merchantCode": "TEST", 
		"serialNo": "20210920164644935780"
	}

JSON GetDomainListResponse:

{
		"domains": [
			"https://lobby1.sample.com", 
			"https://lobby2.sample.com", 
			"https://lobby3.sample.com" 
		]
		"merchantCode": "TEST"
		"code": 0
		"msg": "Success"
		"serialNo": "20210920224255982841"
	}

Example in Http client:

Retrieve Profit Loss List

Usage Scenario: Retrieve profit loss details

Interface Name: getProfitLoss

API Provider: Game Provider

API Requestor: Merchant

Request Message Definition of GetProfitLossRequest:

Response message definition for GetProfitLossResponse:

ProfitLossInfo definition：

GetProfitLoss (Request and response messages example):

JSON GetProfitLossRequest:

{
		"beginDate": "20220901T000000", 
		"endDate": "20220902T000000", 
		"merchantCode": "TEST", 
		"isAll": true, 
		"currency": "CNY", 
		"pageIndex": 1
	}

JSON GetProfitLossResponse:

{
		"list": [{
			"merchantCode": "TEST", 
			"currency": "CNY", 
			"betCount": 149612, 
			"betAmount": 285725.32, 
			"validBetAmount": 285725.32, 
			"totalWL": -7271.78, 
			"jpContributeAmt": 0.0, 
			"jpAmt": 0.000000, 
			"jpTotalWL": -7271.779999, 
			"bonusAmt": 0.0, 
			"bonusBearAmt": 0
		}], 
		"pageCount": 1, 
		"resultCount": 1, 
		"merchantCode": "TEST", 
		"code": 0, 
		"msg": "success", 
		"serialNo": "20230419T1526329782"
	}

Example in Http client:

Retrieve Unfinished Game List

Usage Scenario: Retrieve unfinished game details

Interface Name: getUnfinishedGameLog

API Provider: Game Provider

API Requestor: Merchant

Request Message Definition of GetUnfinishedGameLogRequest:

Response message definition for GetUnfinishedGameLogResponse:

UnfinishedGameInfo definition：

GetUnfinishedGameLog (Request and response messages example):

JSON GetUnfinishedGameLogRequest:

{
		"beginDate": "20220929T000000", 
		"endDate": "20221001T000000", 
		"merchantCode": "TEST", 
		"isAll": true, 
		"acctId": "TestPlayer678", 
		"gameCode": "sShkThaiX2", 
		"pageIndex": 1
	}

JSON GetUnfinishedGameLogResponse:

{
		"list": [{
			"acctId": "TESTPLAYER678@TEST", 
			"loginId": "TestPlayer678", 
			"gameCode": "sShkThaiX2", 
			"merchantCode": "TEST", 
			"unfinishedBonus": 0, 
			"unfinishedFree": 12, 
			"unfinishedFreeMultiplyer": 1, 
			"createDate": "20220929T080000"
		}], 
		"pageCount": 1, 
		"resultCount": 1, 
		"merchantCode": "TEST", 
		"code": 0, 
		"msg": "success, "
		"serialNo": "20230419T2105028176"	
	}

Example in Http client:

Query Online Player Info

Usage Scenario: Retrieve the total number of online players currently active on the platform

Interface Name: getOnlinePlayerInfo

API Provider: Game Provider

API Requestor: Merchant

Request Message Definition of GetOnlinePlayerInfoRequest:

Response message definition for GetOnlinePlayerInfoResponse:

OnlinePlayerInfo definition：

GetOnlinePlayerInfo (Request and response messages example):

JSON GetOnlinePlayerInfoRequest:

{
		"merchantCode": "TEST", 
		"serialNo": "1111-1111-1111" 
	}

JSON GetOnlinePlayerInfoResponse:

{
		{
		"serialNo": "1111-1111-1111", 
		"code": 0, 
		"msg": "Success", 
		"merchantCode": "TEST", 
		"resultCount": 1, 
		"pageCount": 1, 
		"list": [
			{
				"userName": "TESTPLAYER901", 
				"currency": "USD", 
				"acctId": "TESTPLAYER901" 
		}

Example in Http client:

API Tournament Definition

The domain for the tournament is same as the available domain. https://tournament.sampledomain.com

The staging for the tournament. https://tournament_staging.sampledomain.com

The production for the tournament. https://tournament.sampledomain.com

Retrieve Tournament List

Usage Scenario: Get list of available tournaments according to merchant

Endpoint Name: /tournament/get

API Provider: Game Tournament Domain

API Requestor: Merchant

Method: POST

Request Message Definition of Tournament List:

Response message definition for Tournament List:

Tournament List (Request and response messages example):

JSON Request:

{
		"merchant": "TEST", 
		"language": "en_US", 
        "game": "sCandyXmas"
	}

JSON Success Response:

{
        "isShow": true, 
		"info": [
        {
            "id": "1000",
            "name": "Songkran Festival Tournament",
            "startDate": "2023-04-01T00:00:00.000Z",
            "endDate": "2023-04-14T23:59:59.000Z",
            "desc": "Spin & Soak up the Big Wins"
	      }
      ]
    }

JSON Info Not Available Response:

{
        "isShow": false, 
    }

Retrieve Tournament Prize List

Usage Scenario: Get prize list of available tournaments according to merchant and currency

Endpoint Name: /tournament/prize/get

API Provider: Game Tournament Domain

API Requestor: Merchant

Method: POST

Request Message Definition of Tournament Prize List:

Response message definition for Tournament Prize List:

Tournament Prize List (Request and response messages example):

JSON Request:

{
		"tid": "1000", 
		"merchant": "TEST", 
        "currency": "USD"
	}

JSON Response:

[
        { 
        "rank": "1", 
        "prize": "USD$ 500" 
        }, 
        { 
        "rank": "2", 
        "prize": "USD$ 300" 
        }, 
        { 
        "rank": "3", 
        "prize": "USD$ 300" 
        }, 
        { 
        "rank": "4", 
        "prize": "USD$ 200" 
        }, 
        { 
        "rank": "5-10", 
        "prize": "USD$ 100" 
        }
    ]

Retrieve Tournament Rank List

Usage Scenario: Get rank list of tournaments

Endpoint Name: /tournament/rank/get

API Provider: Game Tournament Domain

API Requestor: Merchant

Method: POST

Request Message Definition of Tournament Rank List:

Response message definition for Tournament Rank List:

Tournament Rank List (Request and response messages example):

JSON Request:

{
		"tid": "1000", 
		"merchant": "TEST", 
        "game": "sRoma"
	}

JSON Response:

[
        { 
        "rank": "1", 
        "playerId": "TESTPLAYER1", 
        "score": "771402.857142" 
        }, 
        { 
        "rank": "2", 
        "playerId": "TESTPLAYER2", 
        "score": 3809.523809 
        }, 
        { 
        "rank": "3", 
        "playerId": "TESTPLAYER3", 
        "score": 1000 
        }, 
        { 
        "rank": "4", 
        "playerId": "TESTPLAYER4", 
        "score": 12.619047 
        }, 
        { 
        "rank": "5", 
        "playerId": "TESTPLAYER5", 
        "score": 1.428571 
        }
    ]

Retrieve Tournament Player's Rank

Usage Scenario: Get specific player's rank in tournaments

Endpoint Name: /tournament/rank/player/get

API Provider: Game Tournament Domain

API Requestor: Merchant

Method: POST

Request Message Definition of Tournament Player's Rank:

Response message definition for Tournament Player's Rank:

Tournament Player's Rank (Request and response messages example):

JSON Request:

{
		"tid": "1000", 
		"merchant": "TEST", 
        "playerId": "TESTPLAYER1", 
        "game": "sRoma"
	}

JSON Response:

{
        "score": 3809.523809, 
        "bet": 16000, 
        "rank": 2 
    }

Retrieve Tournament Player's Bet Details

Usage Scenario: Get player's details according to merchant and tournament

Endpoint Name: /tournament/details/get

API Provider: Game Tournament Domain

API Requestor: Merchant

Method: POST

Request Message Definition of Tournament Player's Bet Details:

Response message definition for Tournament Player's Bet Details:

Tournament Player's Bet Details (Request and response messages example):

JSON Request:

{
		"tid": "1000", 
		"merchant": "TEST", 
        "playerId": "TESTPLAYER1", 
        "beginDate": "2022-09-01 00:00:00", 
        "endDate": "2022-09-10 00:00:00", 
        "currency": "USD",
        "pageNo": 1,
        "pageSize": 10
	}

JSON Response:

[
        { 
			"merchant": "TEST", 
			"playerId": "TESTPLAYER1", 
			"currency": "USD",
			"betCount": 19856,
			"ttlBet": 3239892,
			"wlAmt": -3131821.12,
			"score": -771402.857142,
			"rank": 1
        }, 
        { 
			"merchant": "TEST", 
			"playerId": "TESTPLAYER2", 
			"currency": "MYR",
			"betCount": 18,
			"ttlBet": 16000,
			"wlAmt": -6152,
			"score": 3809.523809,
			"rank": 2
        }, 
        { 
			"merchant": "TEST", 
			"playerId": "TESTPLAYER3", 
			"currency": "MYR",
			"betCount": 44,
			"ttlBet": 4200,
			"wlAmt": 28028,
			"score": 1000,
			"rank": 3
        } 
    ]

Retrieve Tournament Player's Result

Usage Scenario: Get player's result according to merchant and tournament

Endpoint Name: /tournament/results/get

API Provider: Game Tournament Domain

API Requestor: Merchant

Method： POST

Request Message Definition of Tournament Player's Result Details:

Response message definition for Tournament Player's Result Details:

Tournament Player's Result(Request and response messages example):

JSON Request:

{
		"tid": "1000", 
		"merchant": "TEST", 
		"currency": "USD"
	}

JSON Response:

[
		{ 
		"merchantCode": "TEST", 
		"playerId": "TESTPLAYER431", 
		"currency": "USD",
		"ttlBet": 6795069,
		"score": 6795069,
		"rank": 1
		"prize": USD$ 2,118		
		}
	]

Tournament Page

Usage: Tournament page.

Endpoint Name：/tournament

API Provider: Game Tournament Domain

API Requestor：Merchant

1. For language, Refer to Appendix-2.
2. Kindly refer 4.15 Domain List to get the latest domain.

Tournament Page Redirect URL and Parameters:

https://tournament.sampledomain.com/tournament?merchant=TEST&lang=en_US&cy=USD&tid=1000

Appendix 1 Response Code Definition

Appendix 2 Language Code Definition

Appendix 3 Currency Code Definition (ISO)

Appendix 4 Cryptocurrency Code Definition (ISO)