Webhooks Overview
Here’s a list of all webhooks available in Limio, with a short description of what each one does.
Last updated
Was this helpful?
Here’s a list of all webhooks available in Limio, with a short description of what each one does.
Last updated
Was this helpful?
Limio's webhooks will send the following object:
Customer
Subscription
Order
Entitlement
Events
Error Reporting
This webhook sends the Limio Customer object whenever a customer is created or updated as part of a new subscription, either through Limio Commerce or Limio for Salesforce.
The Customer object sent in the webhook is described in the following schema:
This webhook is used to receive the Subscription object after a Subscription gets created using the Limio Shop, Limio Self-Service or the Limio for Salesforce.
The Subscription object sent in the webhook is described in the following schema:
The Order object will be sent when the user goes through the action described below (address change, payment method change, subscription offer change...). The Order object sent will look as below:
This webhook is used to receive the Order object after the Address gets updated using the Limio Shop or Limio Self-Service functionalities.
This webhook is used to receive the Order object after the Payment Method gets updated using Limio Self-Service functionalities or Limio for Salesforce.
This webhook is used to receive the Order object after the Subscription Offer gets updated, usually during a switch scenario in Limio Self-Service or Limio for Salesforce.
This webhook is used to receive the Order object after a new Subscription Offer is added, usually during a cancel/save scenario in Limio Self-Service or Limio for Salesforce.
This webhook is used to receive the Order object after the Subscription is cancelled, usually during a cancellation scenario in Limio Self-Service or Limio for Salesforce
This webhook is used to receive the Order object after the Order is submitted by the customer using the Limio Shop.
This webhook is used to receive the Order object after the Customer Details gets updated using Limio Self-Service.
For a cancellation, we recommend using the Order webhook for Subscription Cancellation to update entitlements.
The Entitlement Object sent via webhook will look as below:
This webhook is used to receive the Event object after the Checkout is initiated by the customer using the Limio Shop.
This webhook is used to receive the Event object after the Customer attempted to cancel the subscription.
This webhook is used to receive the Event object after a Payment Method is added by the customer using the Limio Shop.
This webhook is used to receive the Event object after an Address is added by the customer using the Limio Shop.
The Error webhook is used to notify you when a failure occurs during order processing in Limio. It provides visibility into issues across any step of the order orchestration pipeline and can be used to alert external systems or trigger recovery workflows.
Zuora (e.g. subscription and payment creation)
Salesforce (e.g. contact creation)
Entitlement or delivery logic
Internal Limio plugins (e.g. gift redemption, Callout Plugin)
If any of these plugins fails, Limio generates an Error webhook. The Error webhook allows you to capture these failures externally for alerting, logging, or further action.
Go to Settings > General Settings > Webhooks
Under Error Reporting, locate the Error field
Enter the destination URL where the webhook should be sent
Limio will send a POST request to this URL whenever a plugin fails during order processing.
Each POST request includes:
eventId and processEventId: Useful for tracing the order event in Limio
The original order payload (event)
pluginErrorOutput: A list of plugin errors that occurred
The entitlement webhook notifies external systems when entitlements have been updated. It is triggered only when a subscription reaches an Active status, such as after a successful new order.
When a customer places an order in Limio, it is handled by the . This framework breaks down the order into a series of processing steps handled by plugins, such as: