Skip to main content

Event naming

Every event has a type in the form resource.action — for example invoice.paid or offer.accepted. This value appears in the type field of the payload and is how your integration decides what to do with each event. When creating or editing a webhook you can subscribe to any combination of the events below — individually, by category, or all at once.
The data included with an event reflects the permissions of the webhook’s owner. You will only receive events for resources the owner is allowed to see. See Getting Started.

Available events

There is also a special webhook.test event you can trigger manually to verify your endpoint. It is never sent automatically. See Getting Started.