shopline-webhooks

SHOPLINE Webhooks

When to Use This Skill

• How do I receive SHOPLINE webhooks?
• How do I verify SHOPLINE webhook signatures (X-Shopline-Hmac-Sha256)?
• How do I handle orders/create, products/update, or collect/delete events?
• Why is my SHOPLINE webhook signature verification failing?

Verification (core)

SHOPLINE (the SHOPLINE Open Platform, developer.shopline.com) signs every webhook with HMAC-SHA256 of the raw request body keyed on your app secret (Developer Center → App credentials) and sends the digest in the X-Shopline-Hmac-Sha256 header. Use the raw body — parsing JSON first changes the bytes and breaks the signature — and compare timing-safe.

Encoding — verified as lowercase hex. SHOPLINE's docs show a base64 digest in the header example (Shopify-style), while a code sample shows hex. A live delivery settles it: the code sample is right. Confirmed against a real products/create webhook (API version v20240601) by recomputing HMAC-SHA256 over the raw body with the app secret — the header was 64 lowercase hex characters and matched exactly.

The handlers below still accept either encoding, since the documented example disagrees with observed behaviour and SHOPLINE could differ by version or region — but expect hex. To check your own: 64 [a-f0-9] chars is hex; 44 chars ending = is base64.

The topic is in X-Shopline-Topic; the shop domain in X-Shopline-Shop-Domain.

Node:

const crypto = require('crypto');

function verifyShoplineWebhook(rawBody, hmacHeader, secret) {
  if (!hmacHeader) return false;
  const digest = crypto.createHmac('sha256', secret).update(rawBody).digest();
  // Verified hex in practice; base64 kept as a fallback. Timing-safe either way.
  return [digest.toString('hex'), digest.toString('base64')].some((expected) => {
    try {
      return crypto.timingSafeEqual(Buffer.from(hmacHeader), Buffer.from(expected));
    } catch {
      return false;
    }
  });
}