Mark a quote as rejected by the customer
Authentication
JWT issued via POST /api/v1/auth/sign_in. Used by mobile and SPA clients. Revoked tokens are rejected.
Path parameters
Response
OK. The rejected quote (with status: rejected).
Document type discriminator. Always quote on this endpoint.
Quote lifecycle state. issued is ready for external use;
sent has reached the customer; accepted and rejected
record the customer’s decision; expired is past
expiry_date; reopened is where
reopenQuote lands a previously
locked quote (editable again, must be re-sent); canceled
is explicitly retired.
ISO-4217 currency code.
Derived settlement degree. Null for quotes because they are non-payable.
Null for quotes because they are non-payable.
Null for quotes because they are non-payable.
Quote number (formatted via number_series, e.g. ‘CEN2026-0001’). Null for drafts.
Payment due date; typically null for quotes.
Tax scheme (UNCL 5153), e.g. “VAT”.
Delivery/carrier mode
Amount settled so far. Always null for quotes (non-payable type).
Outstanding amount. Always null for quotes (non-payable type).
Origin of the document. null when it was created in Lucanto, in which case totals are Lucanto’s EN 16931 calculation. A non-null value means the document was imported from that system and initially carries the source system’s own figures, preserved verbatim; those may differ by cents from Lucanto’s calculation because systems round VAT at different levels (line vs. category). insight means AI extraction from an uploaded file, not an import from another vendor. This records provenance only, not which calculation is currently in effect — editing line items or document discounts recomputes totals in Lucanto while leaving import_source set. In practice a document only ever carries kros_developer, isdoc, superfaktura or null. kros appears only on rows imported before the writer was renamed, and insight is written by the expense path only. The enum is kept as the union across resources rather than narrowed, so a legacy row cannot fail validation.
The party identity as it appears on a document. On an ISSUED document this is the identity the document was issued with — a snapshot pinned at issue, which does NOT change when the legal entity is later renamed, re-registered, or moved. A draft follows the entity’s current identity. id is the legal entity’s id and is stable across identity changes, so a stored reference keeps resolving. This matches the PDF and the ISDOC export of the same document. vat_period is not part of this projection — a counterparty’s filing period is not knowable.
The party identity as it appears on a document. On an ISSUED document this is the identity the document was issued with — a snapshot pinned at issue, which does NOT change when the legal entity is later renamed, re-registered, or moved. A draft follows the entity’s current identity. id is the legal entity’s id and is stable across identity changes, so a stored reference keeps resolving. This matches the PDF and the ISDOC export of the same document. vat_period is not part of this projection — a counterparty’s filing period is not knowable.

