Event Catalog
110 public webhook events generated from the event contract
2026-06-09110 events
events/public/webhook-event.v1.schema.jsonbilling
invoice.createdAn invoice was created.stablev1invoice.issuedAn invoice was issued.stablev1invoice.paidAn invoice reached paid state.stablev1invoice.payment_failedAn invoice payment attempt failed.stablev1invoice.refundedAn invoice was refunded.stablev1invoice.sentAn invoice was sent to a customer.stablev1invoice.voidedAn invoice was voided.stablev1bookings
booking.cancelledA booking was cancelled.stablev1booking.completedA booking was completed.stablev1booking.confirmedA booking was confirmed.stablev1booking.createdA booking was created.stablev1booking.heldA booking slot was held while payment, review, or another prerequisite is pending.stablev1booking.payment_requiredA booking requires payment before it can continue or be finalized.stablev1catalog
customers
documents
document_request.approvedA document request was approved.stablev1document_request.createdA document request was created.stablev1document_request.rejectedA document request was rejected.stablev1document_request.sentA document request upload link was sent to a customer.stablev1document_request.submittedA document request was submitted.stablev1expenses
forms
hr
inventory
orders
order.cancelledAn order was cancelled.stablev1order.completedAn order reached completed state.stablev1order.createdAn order was created.stablev1order.fulfilledAn order was fulfilled.stablev1order.fulfillment.status_changedAn order fulfillment lifecycle status changed.stablev1order.fulfillment_requestedAn order was sent to a custom fulfillment service.stablev1payments
payment.dispute_closedA payment dispute was closed without a clear won/lost chargeback outcome, such as an inquiry or warning closure.stablev1payment.dispute_lostA payment dispute was resolved against the merchant and may require loss accounting.stablev1payment.dispute_openedA payment dispute or chargeback was opened by the payment provider against a charge. Subscribe to alert your team and begin collecting evidence. The event's `data.object` contains the public dispute resource; see this event's payload schema and example for the exact fields.stablev1payment.dispute_updatedA payment dispute changed — for example its status, stage, evidence deadline, or the provider's details were updated. Subscribe to keep your dispute-handling workflow in sync. The event's `data.object` contains the public dispute resource; see this event's payload schema and example for the exact fields.stablev1payment.dispute_wonA payment dispute was resolved in the merchant's favor.promotions
quotes
selling_plans
shipping
shipping.label_purchasedA shipping label was successfully purchased for an order and is ready to use. Subscribe to this event to drive fulfillment steps such as notifying the customer, advancing the order's status, or recording the shipment's tracking reference. The event's `data.object` contains the public shipping resource; see this event's payload schema and example for the exact fields.stablev1shipping.label_voidedA shipping label was voided.stablev1shipping.shipment_deliveredA shipment was delivered.stablev1subscriptions
subscription.cancelledA subscription was cancelled.stablev1subscription.card_setup_requestedA customer must add or confirm a card for a subscription.stablev1subscription.createdA subscription was created.stablev1subscription.pausedA subscription was paused.stablev1subscription.payment_failedA subscription payment failed.stablev1subscription.renewedA subscription renewed.stable