Webhooks Overview

Receive real-time event notifications from Ordergroove when subscription and order activity occurs

View as Markdown

Ordergroove webhooks let you subscribe to events that happen within the platform — subscription creation, order placement, payment updates, cancellations, and more — and receive HTTP POST notifications to a URL of your choosing in real time.


How Webhooks Work

When a subscribed event occurs in Ordergroove, we send an HTTP POST request to the endpoint URL you’ve configured. The request body contains a JSON payload describing the event and the associated data.

Your endpoint should return a 2xx response to acknowledge receipt. If we don’t receive one, Ordergroove will retry delivery.


Authentication

All webhook payloads are signed so you can verify they originated from Ordergroove. We support two signing methods:

  • HMAC-SHA256 — a hash-based signature included in the request headers
  • AES encryption — payload-level encryption for an additional layer of security

See HMAC and AES Authentication for implementation details.


Configuring Webhooks

Webhooks can be configured through the Ordergroove dashboard or programmatically via the API.

  • For the full list of available events and the configuration API reference, see the endpoint documentation in this section.
  • For a step-by-step setup walkthrough, see Configure Webhooks via API.

Legacy Webhooks

If your integration was built before the current Webhooks API, you may be using the legacy webhook system. See Webhooks Overview (Legacy) for documentation on the older format, and Configure Webhooks via API for migration guidance.


GuideDescription
HMAC and AES AuthenticationVerify webhook payloads are from Ordergroove
Webhooks Overview (Legacy)Legacy webhook format and event list
Configure Webhooks via APIRegister and manage webhook endpoints
Expiring or Termed Subscriptions Using WebhooksHandle subscription expiry events
Using Webhooks for 1-Click ActionsTrigger upsell and action flows from webhooks