Scenario
This API is only needed if external system store member data and needs to sync it with EZR.
Member's points change in external system, external system will update changes to EZR
Direction
External system will call EZR
Call path: api/cvip/vipbonusset
Core Logic
Repeated records will be ignored
Request Parameters
Field | Type | Required | Length | Description |
OldCode | string | At least 1 of 3 is required | 1~16 | Member's unique code (external system) |
Code | string | 1~16 | Member's unique code (in EZR) | |
WxOpenID | string | 0~32 | Member’s WeChat OpenID | |
TransBonus | Int | Yes | positive - add | |
TradeNo | string | Yes | 1~20 | Transaction record, used to trace back and prevent duplication |
ChangeTime | string | Yes | Time when change happens | |
EffectDate | int | Date when points are available to redeem | ||
ValidityDate | int | Yes | Expiration date of points | |
TransOrigin | int | Reason of points change | ||
Remark | string | Yes | 1~32 | Will be used in WeChat template message |
Example Request (JSON)
{
"OldCode": "EZ00001230",
"Bonus": 100,
"BonusTotal": 1000,
"TransBonus": -100,
"TradeNo": "T00001",
"ChangeTime": "2015-11-01 12:30:01",
"Remark": "积分换券",
"EffectDate": 20100101,
"ValidityDate ": 20100105,
} "Remark": "线上手工调整",
Example Return by EZR (JSON)
{
"Status": true,
"StatusCode": 200,
"Msg": "成功",
"Timestamp": "20150622093101",
"Sign": "6ECC9BF07C69E80F6D8552FF7B2E7A8FCA2CC80E",
"Result": 见业务返回结果示例,
}