Platform webhooks SureBright receives
The store-platform events SureBright subscribes to on Shopify, BigCommerce, WooCommerce, Magento, Lightspeed and Shift4Shop, the receiver each one is delivered to, how deliveries are authenticated, and what SureBright does with them.
When you connect a store, SureBright registers webhooks on your platform so contracts follow your orders without any work on your side. This page is the reference list: which events are subscribed, where they are delivered, and how SureBright checks that a delivery is genuine. It is useful when you audit the webhooks on your store, allow-list outbound traffic, or read your platform's delivery logs.
All receivers are under https://{HOST_NAME}/partner/api. They are maintained by SureBright; you never call them yourself, and the subscriptions are re-created if they go missing.
Shopify#
SureBright subscribes 19 topics when the app is installed and keeps them in sync on every reinstall or scope change. The three privacy topics are declared on the app itself rather than subscribed per store.
Every delivery must carry a valid X-Shopify-Hmac-Sha256 signature over the raw body, computed with the app's secret; a bad or missing signature is answered 400 and ignored. Handlers answer 200 once a delivery is accepted, including deliberate no-ops, so Shopify does not retry them.
BigCommerce#
Registered against your store during the first authorization of the SureBright app. Each subscription carries an x-surebright-api-key header that SureBright generates for your store at install time (a signed platform:store token). A delivery whose key is missing, fails the signature check or names another platform is rejected.
A fifth receiver, /v1/webhook/bigCommerce/order/refund, exists for refund events delivered separately; current installs route refunds to /order. See BigCommerce for the install flow.
WooCommerce#
Four order webhooks are registered on your store when the SureBright plugin is connected. Each delivery is checked against x-wc-webhook-signature, the HMAC WooCommerce computes over the raw body with the webhook's secret, and the store is identified from x-wc-webhook-source. A failed signature is answered 400.
Magento#
The SureBright Magento module sends events itself rather than through native Magento webhooks: it observes product saves and order saves and posts to SureBright. Each event carries a store-bound access token (sb-access-token header, or sbAccessToken in the body) issued when the module is connected; the token is verified and must name a Magento store.
See the Magento install guide.
Lightspeed#
X-Series deliveries are accepted when the body carries Lightspeed's type, domain_prefix and payload; the store is resolved from domain_prefix and must be a connected store.
Shift4Shop#
The store is identified from the store URL in the order payload.
Delivery and retries#
A receiver answers
200when it has accepted a delivery, even when it decides to do nothing (store uninstalled, feature off, nothing relevant changed). Platforms retry only on non-2xx responses, so a400from a failed signature is not retried while a500from a transient failure is.Processing is idempotent: the same event delivered twice does not create a second contract.
Deliveries that cannot be parsed or fail validation are recorded with the platform and store so SureBright can investigate; you do not need to resend them.