Store package status changes
| Event Group | Event Identification |
|---|---|
| subscription | subscription/challenged |
Notice of changes in package status under the store
Request Headers
- 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
- before_status stringPackage status before changeExample:
active - business_parameters mapBusiness parametersExample:
{} - create_time longPackage creation timeExample:
1691130777203 - end_time longPackage end time , time stamp ( millisecond )
- merchant_id longMerchant idExample:
2011061373 - start_time longPackage start time , time stamp ( millisecond )
- status stringPackage statusExample:
active - store_id longStore idExample:
1690967538993 - sub_type stringPackage typeExample:
preorder - subscription_id stringPackage idExample:
SUB6053264297034524673
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?