Overview
Quote webhooks notify your application when a quote is issued, sent, accepted (manually or through electronic signature), canceled or deleted - the most requested trigger for staffing tools, provisional revenue tracking and document automation.Quote events are currently in beta: the payload structure may still evolve before general availability.
Payload
Thedata field carries the full quote payload, identical to GET /quotes/{id} - amounts, lines, seller/account/contact blocks, pdf_url, signature included.
quote.validated or quote.sent event: read status (and signature for e-signed quotes) on quote.updated. A quote accepted through electronic signature arrives as a quote.updated with status: "validated" and the signature block filled.
Delivery semantics
- A new version is a new quote. Re-issuing a quote creates a new document (
-v2,-v3… suffix innumber): you receive aquote.createdfor it, and typically aquote.updated(status: "canceled") for the previous version. - Deliveries use the standard envelope, HMAC signature and retry policy - see Webhooks introduction and Security.
Typical integrations
- Staffing / operations (e.g. staff planners): on
quote.updatedwithstatus: "validated", read the quotelinesto extract sold quantities (hours, headcount) and the booking dates viabooking_id→GET /bookings/{id}. - Provisional revenue: accumulate
amount_excl_taxof validated quotes byservice_start_datemonth. - Document automation: on
quote.updatedwithstatus: "sent"or"validated", fetchpdf_urland generate downstream documents without polling.
