REST API

Method: GET/POST, depends on each endpoint specification

Format: JSON

Uri prefix: /gameapi/v2

Example:

POST /gameapi/v2/create_player HTTP/1.1
Content-Type: application/json; charset=utf-8
Host: <api server>
Connection: close
Content-Length: 255

Request:

{
  "merchant_code": "04e17735ba374dcd898746c6ac8118e4",
  "auth_token": "59ddb8dd71f8494485ff200f78bc4dba",
  "username": "merchant.player2",
  "sign": "20fbee96a0f436a6d8386b192a569a27bcc1c689"
}

Response:

{
  "success": true,
  "code": 0,
  "detail": {
    "id": 11216,
    "role": 3,
    "username": "o2p1632998628",
    "company": 11198
  }
}

Standard result:

• success: Boolean, indicates whether the action succeeded. If false, the "message" field provides error details.
• code: Result code, only for backward compatibility.
• message: string, if the operation fails (success: false), this provides the error message. Please refer to Error List for details.
• detail: Response payload details depending on the specific API endpoint.

• Updated monthly based on popularity

Lobby

Classic

Monster

Scratch

Slot

Lottery

Server Domain or IP

Hide the internal server domain or IP from players.

IP Whitelist

Configure allowed IP addresses on your servers.

For the staging environment, it is necessary to add allowed IPs for visiting game front-end through the Back Office.

Merchant Code and Secure Key

Any 32 characters (letters and numbers), provided via email.

Testing key: dd35aPO0bd186dc6ace6We2e0fb48s70

Sign Key

Any 32 characters (letters and numbers), provided via email.

Testing key: dd35aPO0bd186dc6ace6We2e0fb48s70

Signature

1. Always use UTF-8 encoding.
2. Ignore empty fields, fields with value of object type, or fields named sign.
3. Sort all parameter names in alphabetical (ascending) order.
4. Concatenate all non-empty values into a single string (values only, without keys), append the sign key at the end, and then compute the SHA1 hash to obtain the signature.

Signature Example:

Suppose the sign key is SIGN_KEY_EXAMPLE, and we need to sign the following parameter object:

{
  "b": 1.1,
  "a": 1,
  "d": "some string",
  "e": "",
  "c": true,
  "sign": "abcdefg",
  "g": {
    "x": 1,
    "y": 2
  },
  "f": null
}

The signing procedure is as follows:

1. Ignore fields without value, of object type, or named sign:

   {
     "b": 1.1,
     "a": 1,
     "d": "some string",
     "c": true
   }
   

2. Order params by key ascendingly:

   {
     "a": 1,
     "b": 1.1,
     "c": true,
     "d": "some string"
   }
   

3. Concatenate values in the sorted order and append the sign key:

   11.1truesome stringSIGN_KEY_EXAMPLE
   

4. Perform SHA1 hash on the concatenated string to obtain the signature:

   91bef33b208ba98ac2d889b9c4e996651ca58146
   

Authentication

• Retrieve auth_token using merchant_code and secure_key.
• Include auth_token as a parameter when invoking any API endpoint.