Set RTP Control

Sets an RTP control rule for one or more players in a specified game. A new rule cannot be created when the same player already has an incomplete rule for that game.

Request URL

POST {API_URL_ROOT}/RtpControl/Create

Request Parameters

Field Required Type Description
sign YES string Signature computed using the Signature Algorithm.
timestamp YES int UTC timestamp in seconds since 1970-01-01, e.g. 1741837297.
Accept-Language YES string Response language code. See Language List, e.g. zh or en.
Content-Type YES string "application/json; charset=utf-8"

Body

Field Required Type Description
tenantId YES int Unique merchant ID assigned by the platform.
userId YES string Player ID. Multiple player IDs can be submitted in one request, separated by ASCII commas. Every player must already exist, and IDs may contain ASCII characters only.
gameId YES int Game ID. The game must exist and be online.
controlType YES int Control type. See the table below.
changeRtp YES int RTP value to set, e.g. 50 means 50%.
relievedType YES int Release condition type. See the table below.
relievedThreshold YES double Release threshold. Its unit depends on relievedType.

Example

{
  "tenantId": 1,
  "userId": "player001,player002",
  "gameId": 6,
  "controlType": 1,
  "changeRtp": 50,
  "relievedType": 1,
  "relievedThreshold": 10
}

Response Parameters

A standard success response is returned when the operation succeeds. The rule ID is not returned directly; use the Query RTP API to retrieve it.

Example

{
  "isSuccess": true,
  "code": 0,
  "message": "ok"
}

controlType Values

Value Description
1 Losing
2 Winning

relievedType Values

Value Description Unit for relievedThreshold
1 Number of rounds Round
2 Real-time historical RTP Integer RTP value, e.g. 50 means 50%
3 Win/loss amount Amount
4 Specified duration Minute

results matching ""

    No results matching ""