Skip to main content
GET
Search ProposalContractSchedules
A ProposalContractSchedule is a future price change on one quoted contract inside a proposal: a new unit price and the date it takes effect. Each one becomes a scheduled price change on the customer’s real contract when the proposal is accepted. This is where scheduled price changes are managed once a proposal has been created.

Authentication

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 ProposalContractSchedule-List role.

Query Parameters

Pagination & Sorting

integer
default:"1"
The page number to retrieve.
integer
default:"25"
The number of records per page.
string
The property name to sort results by (e.g. Name, CreatedOn).
integer
Sort direction. 0 for ascending, 1 for descending.

Filters

integer
Filter by iD of the quoted contract this price change belongs to; required, and the issuing location of that contract’s proposal owns this record..
integer
Filter by display value for ProposalContract.Quantity..
string
Filter by display value for ProposalContract.Tariff.Name..
integer
Filter by display value for ProposalContract.Proposal.Coworker.Id..
string
Filter by display value for ProposalContract.Proposal.Coworker.FullName..
string
Filter by display value for ProposalContract.Proposal.Coworker.BillingName..
string
Filter by free-text note explaining the price change; it is carried onto the customer contract’s schedule on acceptance..
number
Filter by new per-unit price that takes effect on ApplyOn, in the issuing location’s currency..
string
Filter by date the new price takes effect; required, and each price change on the same quoted contract needs its own date..
boolean
Filter by read-only flag recording whether this price change has already been applied; the billing run sets it and it is not changed through proposal administration..

Range Filters

integer
Filter by display value for ProposalContract.Quantity. greater than or equal to this value.
integer
Filter by display value for ProposalContract.Quantity. less than or equal to this value.
integer
Filter by display value for ProposalContract.Proposal.Coworker.Id. greater than or equal to this value.
integer
Filter by display value for ProposalContract.Proposal.Coworker.Id. less than or equal to this value.
number
Filter by new per-unit price that takes effect on ApplyOn, in the issuing location’s currency. greater than or equal to this value.
number
Filter by new per-unit price that takes effect on ApplyOn, in the issuing location’s currency. less than or equal to this value.
string
Filter by date the new price takes effect; required, and each price change on the same quoted contract needs its own date. greater than or equal to this value. Format: YYYY-MM-DDTHH:mm.
string
Filter by date the new price takes effect; required, and each price change on the same quoted contract needs its own date. less than or equal to this value. Format: YYYY-MM-DDTHH:mm.
string
Filter records created on or after this date. Format: YYYY-MM-DDTHH:mm.
string
Filter records created on or before this date. Format: YYYY-MM-DDTHH:mm.
string
Filter records updated on or after this date. Format: YYYY-MM-DDTHH:mm.
string
Filter records updated on or before this date. Format: YYYY-MM-DDTHH:mm.

Code Examples

Simple listing

Filtering by CreatedOn

Range filters

Response

200

ProposalContractSchedule[]
The list of ProposalContractSchedule records matching the query. See the Get one ProposalContractSchedule endpoint for the full list of properties returned for each record.
Partial records — The listing endpoint returns a summary representation of each ProposalContractSchedule. The following fields are not populated in the Records[] response: Notes.To get all fields, fetch the full record using the Get one ProposalContractSchedule 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.
integer
Current page number.
integer
Number of records per page.
string
The field used for sorting.
integer
The sort direction (0 = ascending, 1 = descending).
integer
Index of the first item on the current page.
integer
Index of the last item on the current page.
integer
Total number of matching records across all pages.
integer
Total number of pages.
boolean
Whether there is a next page of results.
boolean
Whether there is a previous page of results.
Example Response