1. About Merchants

• All APIs are provided by the POP platform for carrier access and calling.
• After approval of account opening requirements, we will provide a carrier backend account. Carriers can view the AppID (Merchant Number) and AppSecret (Merchant Code) through the backend.
• POP server time zone: UTC+0, pay attention to time zone calculation when accessing data statistics.
• APIs provided by POP: code returns 0 indicates success.

2. Common Parameters (Required for All API Calls by Platform to Merchant)

• API URL, AppID, and AppSecret in the document will be provided by us after carrier application.
• All interface requests need to add 2 Headers: AppID and AppSecret.

• Example:
  API URL: https://XXXXXXXXXXXX.XXXXXXX.XXX
  AppID: XXXXXXXX
  AppSecret: XXXXXXXXXXXX

3. Interface Protocol

• Request data Header sets Content-Type: application/json.
• All interfaces use POST.
• Return JSON in fixed {“code”:int, error: string, data: object} format, code not equal to 0 indicates an error, data field should not be used in this case, code:0 indicates success, when code is not 0, error represents the error description.
• Datetime uses RFC3339 format.
• Can use [mockapi] for testing
  Note: Only focus on interfaces under /api/v1/

4. Request

• Content-Type when requesting platform: “application/json;charset=UTF-8”

5. Call Return

• When the platform returns http code 200, the HTTP API access is normal and the return result can be parsed normally. Other http errors indicate a link exception.
• When the call returns normally, the returned Content-Type is: “application/json;charset=UTF-8”.

复制{
  "code": 0,
  "error": "",
  "data": {
    "glist": [
      {
        "gameid": "9",
        "name": "mine",
        "platform": "1"
       }
      ]
     }
   }

Return Parameter Description

6. Error Code