Marketing Activity Change Callback
Updated: 2025-04-21 15:21:49
Purpose
After a user creates or modifies a marketing activity (task reward, lottery), the server will submit the task processing status to the user-defined callback interface via the POST method.
Callback Failure Retry
- If the interface does not return an HTTP status 200 code, it will be considered that the user failed to process this callback. In case of failure, the callback will be retried 3 times.
Callback Parameter Description
Marketing Activity Change Callback
- Request Method: POST
URL Parameters
| Parameter | Type & Range | Description |
|---|---|---|
| timestamp | long | 13-digit timestamp |
| sign | string | Signature. The signature generation rule is MD5(appSecret + timestamp). To prevent callback request forgery, please verify the correctness of the sign value. |
BODY Parameters:
| Parameter | Type & Range | Description |
|---|---|---|
| activityId | String | Activity ID |
| channelId | string | Channel ID |
| activityType | string | Activity type (TASK_REWARD: task reward, LOTTERY_ACTIVITY: lottery template, LOTTERY: initiate lottery) |
| changeType | string | Change type (CREATE: create, MODIFY: modify, DELETE: delete) |
Callback Data Example
Request address example: https://www.example.com/xxx/callback?sign=d5079f2e8ba19e49bfd3d9575866d80f×tamp=1701964858687
Request body (body parameter: application/json) example
{
"activityId": "1000",
"channelId": "2974342",
"activityType": "TASK_REWARD",
"changeType": "CREATE"
}
How to Configure
Configure via the backend:
Log in to your account - Go to [Cloud Live] - Click [Developer Settings] - Click [Callback Settings] - Marketing Activity Change Callback
Note: The submitted interface address must start with http:// or https://
