Event GroupEvent Identification
appsubscriptionappsubscription/paid
When the merchant subscribe to the Product in the application , the platform will push relevant subscription payment results information to developers
Request Headers
  • X-Shopline-Topic string required
    Event operation identification
    Example: orders/edited
  • X-Shopline-Hmac-Sha256 string required
    Signature
    Example: XWmrwMey6OsLMeiZKwP4FppHH3cmAiiJJAweH5Jo4bM=
  • X-Shopline-Shop-Domain string required
    Shop domain
    Example: shophub.myshopline.com
  • X-Shopline-Shop-Id string required
    Shop ID
    Example: 1610418123456
  • X-Shopline-Merchant-Id string required
    Merchant ID
    Example: 2000001234
  • X-Shopline-API-Version string required
    Version
    Example: v20210901
  • X-Shopline-Webhook-Id string required
    Message ID
    Example: b54557e48a5fbf7d70bcd043
Request Body
  • appkey string
    Apply unique logo
  • bizOrderNo string
    Business order number
  • handle string
    Store unique logo
  • secondChannelId string
    Secondary channel id
  • status integer
    Payment Status, with enumerated values:
    • 200 - Payment Successful
    • 300 - Payment Cancelled
    • 400 - Payment Failed
  • subId string
    Created the order number generated during the subscription
  • subTime long
    Payment time
Response
After receiving a webhook notification from SHOPLINE, you must respond with the following format:
HTTP/1.1 200 OK
For more information about how to subscribe to webhooks and webhook response rules, refer to Webhook overview.
Was this article helpful to you?