Skip to content

Event catalogue

A webhook’s type field selects which Quiddly events it receives. Subscribe to one event type per webhook - the same URL can be reused across multiple subscriptions.

typeWhen it fires
INVOICEAn invoice was created or its status changed.
INVOICE_CREATEDA new invoice was created (subset of INVOICE, useful when you only care about origination).
INVOICE_BALANCEThe outstanding balance on an invoice changed (payment matched, write-off, etc.).
INVOICE_REFINANCEAn invoice was refinanced (factoring lifecycle).
FACTORING_STATUSA factoring agreement transitioned state.
DISTRIBUTIONA document was distributed (email, post, e-invoice channel).
PAYOUT_FILE_XMLA SEPA/payouts XML file was generated and is ready for download.
PAYOUT_FILE_TXTSame as above for the legacy plaintext format.
BOOKKEEPING_FILE_SIEA Swedish SIE bookkeeping file is ready.
VOUCHERA bookkeeping voucher was finalized.
VOUCHER_PAYMENTA payment voucher was generated.
SYSTEM_DEBTORA system-debtor record was created or updated.
CREDIT_CHECKA credit-check result is available.
TRANSACTION_MONITORINGAML transaction-monitoring flagged a transaction.
BUSINESS_LOAN_CREATEDA business loan was created.
BUSINESS_LOAN_MAIN_STATUSA business loan main status changed.
BUSINESS_LOAN_BALANCEThe outstanding balance on a loan changed (payment matched, write-off, etc.).
BUSINESS_LOAN_CREDIT_DECISION_STATUSA business loan credit decision status changed.

The valid values are enforced by the WebhookTypes enum in the API and returned in the 400 response if you send an unknown one.

Each delivery POSTs the resource snapshot Quiddly captured at trigger time as JSON in the request body. The shape is the same as the resource’s GET response - see the reference for the type that matches your subscription. The delivery is identified by the X-Webhook-Id header, not by a field in the body.