A Proposal bundles one or more contracts (ProposalContract records) that are presented to a customer for review and acceptance. Each ProposalContract carries the same properties as a CoworkerContract and becomes one when the proposal is accepted.When a Proposal is created, a ProposalContract is automatically created and associated with it. From that point on, the contract-related fields on the Proposal (TariffId, Desks, Variants, Price, StartDate, CancellationLimitDays, ContractTerm, CancellationDate, ExpirationDate, BillingDay, Quantity) become read-only — they are all createOnly. Subsequent edits to those values must be made via the associated ProposalContract. Additional ProposalContract records can also be added.Proposals support three optional attachments:
DocumentToSendId — a DocumentTemplate entity presented to the customer instead of the standard price-schedule table before the proposal is accepted.
DocumentToSignId — a DocumentTemplate entity used to generate a document for e-signature.
ProposalFile — a file shown as a downloadable link before the proposal is accepted.
Set DoNotIssueInvoice to control whether the first invoice is issued automatically when the proposal is accepted.
This endpoint requires OAuth2 authentication. Include a valid bearer token in the Authorization header.
The authenticated user must be a full unrestricted administrator or have the Proposal-List role.
Filter by start date for the initial contract. Becomes read-only after creation; edit via ProposalContract greater than or equal to this value. Format: YYYY-MM-DDTHH:mm.
Filter by start date for the initial contract. Becomes read-only after creation; edit via ProposalContract less than or equal to this value. Format: YYYY-MM-DDTHH:mm.
Filter by cancellation limit in days for the initial contract. Becomes read-only after creation; edit via ProposalContract greater than or equal to this value.
Filter by cancellation limit in days for the initial contract. Becomes read-only after creation; edit via ProposalContract less than or equal to this value.
Filter by contract term end date for the initial contract. Becomes read-only after creation; edit via ProposalContract greater than or equal to this value. Format: YYYY-MM-DDTHH:mm.
Filter by contract term end date for the initial contract. Becomes read-only after creation; edit via ProposalContract less than or equal to this value. Format: YYYY-MM-DDTHH:mm.
Filter by cancellation date for the initial contract. Becomes read-only after creation; edit via ProposalContract greater than or equal to this value. Format: YYYY-MM-DDTHH:mm.
Filter by cancellation date for the initial contract. Becomes read-only after creation; edit via ProposalContract less than or equal to this value. Format: YYYY-MM-DDTHH:mm.
Filter by proposal expiration date. Becomes read-only after creation; edit via ProposalContract greater than or equal to this value. Format: YYYY-MM-DDTHH:mm.
Filter by proposal expiration date. Becomes read-only after creation; edit via ProposalContract less than or equal to this value. Format: YYYY-MM-DDTHH:mm.
Filter by billing day of month for the initial contract. Becomes read-only after creation; edit via ProposalContract greater than or equal to this value.
The list of Proposal records matching the query. See the Get one Proposal endpoint for the full list of properties returned for each record.
Partial records — The listing endpoint returns a summary representation of each Proposal. The following fields are not included in the Records[] response: Notes, DocumentToSignHtml, DocumentToSendHtml, Price, StartDate, CancellationLimitDays, CancellationDate, BillingDay, Quantity.To get all fields, fetch the full record using the Get one Proposal endpoint.Important for updates: When updating a record via PUT, always retrieve the full record with a GET request first, apply your changes to that complete data, and then send the updated record. Do not use data from a listing response as the base for a PUT request, as missing fields may be unintentionally cleared.