Skip to main content

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

The data field carries the full quote payload, identical to GET /quotes/{id} - amounts, lines, seller/account/contact blocks, pdf_url, signature included.
There is no dedicated 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 in number): you receive a quote.created for it, and typically a quote.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.updated with status: "validated", read the quote lines to extract sold quantities (hours, headcount) and the booking dates via booking_idGET /bookings/{id}.
  • Provisional revenue: accumulate amount_excl_tax of validated quotes by service_start_date month.
  • Document automation: on quote.updated with status: "sent" or "validated", fetch pdf_url and generate downstream documents without polling.