Player Point Control (RTP Adjustment)

Used to control the RTP for a single player or multiple players. It also allows merchants to enable or disable this function for individual or multiple players, and to configure whether point control should be automatically canceled when a player’s historical RTP approaches the preset RTP.

Point control will also automatically expire after 15 days.

OMG server time zone: UTC+0. Integrators should be mindful of time zone calculations when processing data statistics.

RtpControl

This API is provided by the OMG platform and is called by the integrator.

POST {OMG_BACKEND_URL}/api/v1/merchant/outer/rtp/control?trace_id=your_trace_id

{OMG_BACKEND_URL} is the API configuration interface in the merchant backend where the domain for backend API calls can be obtained.

Headers

Name	Value
Content-Type	"application/json; charset=utf-8"
sign	"your_sign_string"

Please refer to the Signature Algorithm and Example page for details on the signature algorithm.

Body

Name	Type	Description
app_id	string	The unique identifier for the merchant, available in the merchant backend.
uname	string	User ID, matches the uname field used for player verification in the game. For multiple users, separate with commas, e.g., 106625,106626.
rtp	integer	When RTP is turned off, it does not need to be provided. Values: 7000, 7500, 8000, 8500, 9000, 9200, 9300, 9400, 9500, 9600, 9700, 9900 correspond to 70%–99% respectively.
switch	integer	Current switch: 1 = off, 2 = on. For example, when switch = 2, the RTP needs to be provided.
auto_cancel	integer	Whether to automatically cancel point control after reaching the specified RTP. 0 - Do not automatically cancel, 1 - Automatically cancel, default is 1.

Integrator Request Parameter Example (Single User)

{
    "app_id": "10013",
    "uname": "1004613",
    "rtp": 9000,
    "switch": 2,
}

Integrator Request Parameter Example (Multiple User)

{
    "app_id": "10013",
    "uname": "1001726,1003401,1003402,1001719,1001720,1001721",
    "rtp": 9000,
    "switch": 2,
}

OMG Platform Response Parameter Example

Success

{
    "code": 1,
    "msg": "success"
}

Failed

Response Example Parameter Descriptions

Name	Requied	Type	Description
code	Yes	integer	Status Code
msg	Yes	string	Message

Error Code

For more error codes, please refer to the Special Error Code page description.