Webhook events¶
Webhook events¶
| Event type | Meaning |
|---|---|
bill.created |
A new bill was created. |
bill.updated |
A bill was updated, approved or voided. |
connection.created |
Your app was granted a new connection to an organisation. |
connection.revoked |
A connection to an organisation was revoked. |
contact.created |
A new contact was created. |
contact.updated |
A contact was updated, merged or archived. |
credit_note.created |
A new credit note or supplier credit was created. |
credit_note.updated |
A credit note or supplier credit was updated or voided. |
invoice.created |
A new invoice was created. |
invoice.updated |
An invoice was updated, approved or voided. |
migration.batch.completed |
A LuciMigration import batch finished (success, partial or failed). |
Subscribe to the specific event_types you need — you don't get every
event by default.
ping¶
A reserved ping event type also exists. It is never subscribable via
event_types and is not in the catalogue above — it is sent only by the
"Send test event" action in the developer portal (and the POST
/api/v1/webhooks/subscriptions/<id>/ping API), so you can confirm your
receiver is reachable and your signature verification works before relying
on real events. Treat a ping delivery like any other: verify its
signature the same way, and don't assume its shape matches a catalogue
event's payload.