Auto Nurturing for New Players

This feature is a toggle. When enabled, all newly registered players will enter the nurturing state until they reach the preset nurturing amount.

It can be applied to all newly registered players simultaneously, meeting the management needs of large-scale profit targets.

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

AutoConfig

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

POST {OMG_BACKEND_URL}/api/v1/merchant/outer/patron/auto/config?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	Use the merchant appid obtained from the backend. For multi-currency merchants, pass the corresponding sub-merchant appid.
patron_status	string	0 — Off 1 — On
patron_amount	integer	The nurturing amount (for each player), with the unit based on the merchant’s currency type. Supported range: 0.01–1,000,000. When passing the parameter, the value must be multiplied by 10,000.
is_cancel_all	integer	When patron_status = 1, no value is required. When patron_status = 0, passing 0 performs no additional action, while passing 1 cancels the nurturing status of all players currently being nurtured through the auto-nurturing feature.
patron_type	integer	Customer nurturing parameter. This parameter must be provided when type = 14. 0: Fast customer nurturing 1: Slow customer nurturing

If multiple users and multiple games are specified, control will be applied/canceled across multiple games for multiple users.

Integrator Request Parameter Example

{
    "app_id":"1001",
    "patron_status":0,
    "patron_amount":1000,
    "is_cancel_all":1,
}

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.