Event Types
This is the full list of webhook events available in Lemon Squeezy.
| Event Name | Data Sent | Description |
|---|---|---|
order_created | Order object | Occurs when a new order is successfully placed. |
order_refunded | Order object | Occurs when a full or partial refund is made on an order. |
subscription_created | Subscription object | Occurs when a new subscription is successfully created. An order_created event will always be sent alongside a subscription_created event. |
subscription_updated | Subscription object | Occurs when a subscription’s data is changed or updated. This event can be used as a “catch-all” to make sure you always have access to the latest subscription data. |
subscription_cancelled | Subscription object | Occurs when a subscription is cancelled manually by the customer or store owner. The subscription enters a “grace period” until the next billing date, when it will expire. It is possible for the subscription to be resumed during this period. |
subscription_resumed | Subscription object | Occurs when a subscription is resumed after being previously cancelled. |
subscription_expired | Subscription object | Occurs when a subscription has ended after being previously cancelled, or once dunning has been completed for past_due subscriptions. You can manage how long to wait before the system marks delinquent subscriptions as expired. More info |
subscription_paused | Subscription object | Occurs when a subscription’s payment collection is paused. |
subscription_unpaused | Subscription object | Occurs when a subscription’s payment collection is resumed after being previously paused. |
subscription_payment_success | Subscription invoice object | Occurs when a subscription payment is successful. |
subscription_payment_failed | Subscription invoice object | Occurs when a subscription renewal payment fails. |
subscription_payment_recovered | Subscription invoice object | Occurs when a subscription has a successful payment after a failed payment. A subscription_payment_success event will always be sent alongside a subscription_payment_recovered event. |
subscription_payment_refunded | Subscription invoice object | Occurs when a subscription payment is refunded. |
license_key_created | License key object | Occurs when a license key is created from a new order. An order_created event will always be sent alongside a license_key_created event. |
license_key_updated | License key object | Occurs when a license key is updated. |
Recommended minimum webhooks
We suggest subscribing to these events as a minimum so that your application will have the latest data.
Single payment
order_created - This event lets you know when new orders are placed.
Subscriptions
subscription_created - This event lets you know when new subscriptions are created.
subscription_payment_success - This event lets you save billing histories for your subscribing customers.
subscription_updated - This event keeps your application up-to-date with all changes to a subscription.
Events sent during a subscription’s lifecycle
Different events will be triggered at various events during a subscription’s life.
You can see that subscription_updated is fired at every event after the initial payment. In most cases, subscribing to more granluar events like subscription_resumed or subscription_expired events as well as subscription_updated is not necessary.
Example 1: A typical flow of events
Initial order is placed:
order_createdsubscription_createdsubscription_payment_successlicense_key_created(if licenses are enabled on the subscription product)
Successful renewal payment:
subscription_payment_successsubscription_updated
Payment method updated by customer:
subscription_updated
Subscription manually cancelled by the customer or store owner:
subscription_cancelledsubscription_updated
Subscription expires when the cancelled subscription reaches the ends_at date:
subscription_expiredsubscription_updated
Example 2: With payment failures
Initial order is placed:
order_createdsubscription_createdsubscription_payment_successlicense_key_created(if licenses are enabled on the subscription product)
Successful renewal payment:
subscription_payment_successsubscription_updated
Failed renewal payment (attempt 1):
subscription_payment_failedsubscription_updated
Successful renewal payment:
subscription_payment_successsubscription_payment_recoveredsubscription_updated
Failed renewal payment (attempt 1):
subscription_payment_failedsubscription_updated
Failed renewal payment (attempt 2):
subscription_payment_failedsubscription_updated
Failed renewal payment (attempt 3):
subscription_payment_failedsubscription_updated
Failed renewal payment (attempt 4):
subscription_payment_failedsubscription_updated
(Subscription enters dunning)
Dunning finishes:
subscription_expiredsubscription_updated