Webhook Events
Our webhook events and in which context they are useful
Billing Events
Checkout
checkout.created
checkout.updated
Customers
customer.created
Fired when a new customer has been created.
customer.updated
Fired when a customer has been updated.
customer.deleted
Fired when a customer has been deleted.
customer.state_changed
Fired when a customer’s state has changed. Includes active subscriptions and granted benefits.
Subscriptions
In order to properly implement logic for handling subscriptions, you should look into the following events.
subscription.created
Fired when a new subscription has been created.
subscription.updated
Use this event if you want to handle cancellations, un-cancellations, etc. The
updated event is a catch-all event for subscription.active ,
subscription.canceled, subscription.uncanceled and subscription.revoked.
order.created
In case you want to do logic when a subscription is renewed, you should listen
to order.created and the billing_reason field. It can be purchase,
subscription_create, subscription_cycle and subscription_update.
subscription_cycle is used when subscriptions renew.
subscription.active
subscription.canceled
subscription.uncanceled
subscription.revoked
Order
order.created
order.paid
order.updated
order.refunded
Refunds
refund.created
refund.updated
Benefit Grants
benefit_grant.created
benefit_grant.updated
benefit_grant.revoked
Organization Events
Benefits
benefit.created
benefit.updated
Products
product.created
product.updated
Organization
organization.updated
Was this page helpful?