invoice.created, invoice.updated, invoice.deleted, invoice.sundry, and invoice.activity. Use invoice.updated to track significant state transitions such as publishing, payment, or cancellation; use invoice.sundry for lower-significance field edits such as category or tag changes; and use invoice.activity to react to file attachments. Note that recording a payment that fully settles an invoice fires both a payment.created event and an invoice.updated event with change: "paid" — subscribe to both if your integration needs to act on each fact separately.
The webhook envelope structure, delivery behaviour, and retry logic are documented in Introduction. Signature verification is covered in Verification. Those conventions apply to every event on this page and are not repeated here.
The invoice object
Every event key exceptinvoice.deleted carries the full invoice object. In invoice.created the object appears flat inside data; in invoice.updated and invoice.sundry it is nested under data.invoice.
Line item fields
invoice.created
Fires when an invoice is created, including when an existing invoice is cloned. data is the full invoice object.
invoice.updated
Fires when a significant change is made to an invoice. Read data.change to determine what changed; data.invoice contains the full invoice object reflecting its state after the change.
invoice.sundry
Fires when a minor or cosmetic field is edited. Read data.field to determine which field changed; data.invoice contains the full invoice object.
invoice.activity
Fires when a child record on the invoice changes. Invoices produce only type: "attachment" — invoices are not part of the core comment system. Read data.action to distinguish additions from deletions.
invoice.deleted
Fires after the invoice is permanently deleted. Because the record no longer exists, data contains only the invoice id.
