Transfer
JDB Platform API
Report-Related
Action 54: Query Game Result

Action 54: Query Game Result

Function Description

  • Query the player game results
  • Query without gType and historyId : Report main page will be displayed.
  • If both gType and historyId are specified: the detailed game result of the given historyId will be displayed, but note the following:
    • For detailed game result from JDB, GTF, INJOY game provider, the result will be available 1 minute after player finished the game round.
    • For detailed game result from game providers not in the previous list, the result be available 6 minutes after player finished the game round.
  • Game result URL valid for 30 seconds.
  • About socket timeout setting, it is recommended to set more than 40 seconds for testing environment and 20 seconds for production environment.
  • Query the data of JDB game provider, the time range should be within 30 days.
  • Query the data of SPRIBE game provider, the time range should be within 30 days.
  • Query the data of GTF game provider, the time range should be within 30 days.
  • Query the data of FC game provider, the time range should be within 60 days.
  • Query the data of AMB game provider, the time range should be within 7 days.
  • Query the data of SWG game provider, the time range should be within 90 days.
  • Query the data of YB game provider, the time range should be within 60 days.
  • Query the data of HRG game provider, the time range should be within 40 days.
  • Query the data of ONLYPLAY game provider, the time range should be within 180 days.
  • Query the data of INJOY game provider, the time range should be within 30 days.
  • Query the data of CREEDROOMZ game provider, the time range should be within 30 days.
  • Query the data of MANCALA game provider, the time range should be within 60 days.
  • Query the data of ZESTPLAY game provider, the time range should be within 30 days.
  • Query the data of SMARTSOFT game provider, the time range should be within 120 days.

Parameter

ParameterFormatMandatoryDescription
actionIntegerY54
tsLongYCurrent system time
parentString(50)YAgent ID
uidString(50)YPlayerID
langStringNLanguage
Given any language that is not in the list above will be treated as English by default.

See Language Code
gTypeIntegerNGame types
“gType” is needed when searching the single game detail.

See Game Provider
historyIdString(100)NGame History ID
“historyId” is needed when searching the single game detail.

See Explanation of historyId
showUidIntegerNWhether show player id
0: not show id
1: show id (default)

Example

{
  "action":54,
  "ts":1447452951820,
  "parent":"testag",
  "uid":"testpl01",
  "gType": 0,
  "historyId":"1234567890"
}

Return Results

ParameterFormatDescription
statusString(4)Success: 0000

Error: See Error Codes in Appendix
dataJSON ArrayThe returned data will be listed in the following table.
err_textString(255)Error message

Data Object

ParameterFormatDescription
pathStringGame result URL

Operation Sample

// Http Request
http://{API_Address}/apiRequest.do?dc=jb1&x=y1wayxScczy6ABfElfaVwb5CdfHxBN_JGtxyBSvpohLQakP8M2QSetJNojJBzvnrVChhq8YWWgBTdGeXFTH4vSNQQ66epf4NqYeQ-6bJ15pvHctQjQevulv7GHqOifuju_gY0H54FfVdQc9D5tKh1AZ-9KDh9dwcGSszZxU7JOOoHdYITlCO5LhvGmHxPBwZ
 
// Http Response (success)
{
"status":"0000",
"data": [
    {
      "path":"https://xxx.xxx.xxx/...."
    }
  ]
}
 
// Http Response (error)
{
  "status":"9005",
  "err_text":"Assertion(SAML) didn't pass the timestamp validation."
}