Proposal history
The unique merchant proposal id
The page at which the proposal versions should be returned
0The maximum number of proposal versions to return
10Filters the history version by statusComment field. It can be "true" or "false"
application/jsonExample: application/jsonPossible values: Authentication header
code="{VENDOR_CODE}" date="{REQUEST_DATE_TIME}" hash="{HASH}"OK
The incoming page value
0The incoming limit value
10The total number of proposal versions matching the criterias
1OK
The unique merchant proposal id
The proposal version
application/jsonExample: application/jsonPossible values: Authentication header
code="{VENDOR_CODE}" date="{REQUEST_DATE_TIME}" hash="{HASH}"OK
The unique merchant proposal id
FDG123The version of the proposal. Every modification increments the version by 1.
1The UTC creation date for the proposal in ISO 8601 format
2020-01-05T17:21:42ZThe UTC last update date for the proposal in ISO 8601 format
2020-01-05T17:21:42ZThe unique external system user identifier
john.doe@customer.comThe unique external system user identifier
john.doe@customer.comIf the proposal is locked for buy modifications
falseThe source from where the proposal was created
SALESFORCE_CPQThe name of the proposal
Renewal of antivirusThe type of the proposal
acquisitionExample: acquisitionPossible values: The status of the proposal
openedPossible values: The UTC expiration date for the proposal in ISO 8601 format. Set only when the status is changed to "sent".
2020-01-05T17:21:42ZThe associated comment for the status
The price is too high for the first productBad Request
Unauthorized
Not Found
Internal Server Error
Last updated
Was this helpful?