Points updated
| Event Group | Event Identification |
|---|---|
| app_memberSystem_points | app_memberSystem_points/challenged |
Occurs whenever member points are changed.
Request Headers
- Content-Type string requiredThe field must be set to the fixed value
application/json; charset=utf-8. - X-Shopline-Topic string requiredThe unique identifier for the event.Example:
orders/edited - X-Shopline-Hmac-Sha256 string requiredThe signature of the request. Upon receiving the request, you must verify the signature to confirm the authenticity and integrity of the data.Example:
XWmrwMey6OsLMeiZKwP4FppHH3cmAiiJJAweH5Jo4bM= - X-Shopline-Shop-Domain string requiredThe store domain.Example:
example.myshopline.com - X-Shopline-Shop-Id string requiredThe store ID.Example:
1610418123456 - X-Shopline-Merchant-Id string requiredThe merchant ID.Example:
2000001234 - X-Shopline-API-Version string requiredThe API version.Example:
v20250601 - X-Shopline-Webhook-Id string requiredThe ID of this Webhook event.Example:
b54557e48a5fbf7d70bcd043
Request Body
- buyer_id stringBuyer ID.Example:
2404721679 - points_balance longAvailable points.Example:
20 - points_expiry_time longThe expiration time of the points changed in this transaction. It has a value only when
updateTypeisINCREASE.Example:1721829526566 - store_id stringStore ID.Example:
1718263946864 - update_type stringPoints change type. Valid values are:
INCREASE: Points increase.DECREASE: Points decrease.
Example:DECREASE - updated_at longThe update time of this transaction record.Example:
1721829526566 - updated_scene stringPoints change scenario. Valid values are:
SUCCESSFUL_REGISTRATION: Customers get points after registration.LOGIN_SUCCESS: Customers get points after successful login.CUSTOMERS_BIRTHDAY: Customers get points on their birthdays.SUCCESSFUL_ORDERS: Customers get points after successfully placing orders.EMAIL_SUBSCRIPTION: Customers get points by subscribing to emails.ENTER_PHONE: Customers get points by filling in their phone numbers.ENTER_BIRTHDAY: Customers get points by filling in their birthdays.SHARE_FB: Customers get points by sharing on Facebook.FOLLOW_FB: Customers get points by following on Facebook.FOLLOW_INS: Customers get points by following on Instagram.DAILY_ATTENDANCE: Customers get points by checking in daily.PRODUCT_REVIEWS: Customers get points by reviewing products.TOP_REVIEWS: Customers get points for a product review selected as high-quality.CUSTOMIZED_RULE: Customized points rules.LEVEL_MEM_BENEFITS: Customers get points based on membership level benefits.PAID_MEM_BENEFITS: Customers get points based on paid membership benefits.SUCCESSFUL_REFERRAL: Customers get points for successful referrals.MANUALLY_INCREASE: Merchants manually add points for customers.CUSTOMER_IMPORT_INCREASE: Merchants manually add points when importing members.CASHBACK: Points are deducted to offset the payment.REDEEM_COUPON_CODE: Points are deducted to redeem percentage-off coupons.REDEEM_COUPON: Points are deducted to redeem fixed-amount vouchers.REDEEM_FREE_SHIPPING: Points are deducted to redeem free-shipping coupons.REDEEM_PRODUCTS: Points are deducted to redeem products.MANUALLY_DECREASE: Merchants manually deduct points from customers' accounts.CUSTOMER_IMPORT_DECREASE: Merchants deduct points from members' accounts when they manually import members.POS_DECREASE: Points are deducted via the POS terminal.POINTS_EXPIRED: Points are invalidated due to expiration.ORDER_RETURN: Points are returned for order refund.REFUND_POINT_BY_EXCHANGE: Cancel the redemption and receive a refund of points.
Example:SUCCESSFUL_REGISTRATION - updated_value longThe amount of points changed.Example:
20
Status Codes
After receiving a webhook notification from SHOPLINE, you must respond with the following format:
HTTP/1.1 200 OKFor more information about how to subscribe to webhooks and webhook response rules, refer to Webhook overview.
Was this article helpful to you?