Request
POST /public/proposals/{ProposalId}
Headers
Must be
application/json.Must be
application/x-www-form-urlencoded.Your API Application Key.
Your User API Key obtained from the authentication exchange.
Current UTC timestamp in RFC 7231 format, e.g.
Mon, 06 Apr 2026 00:22:19 GMT.HMAC-SHA256 signature of the canonical request message, Base64-encoded.
Path Parameters
The unique numeric ID of the proposal to update. Must belong to the current account.
Body Parameters
New display name for the proposal. If omitted, the current name is retained.
ID of the new salesperson to assign. Must be a user in the current account. If omitted, the current salesperson is retained.
A
409 Conflict is returned if the proposal is in a terminal state (e.g. accepted, cancelled) that prevents editing. Check the proposal’s status field before attempting updates.Response
200 Success
Returns the full updated proposal detail object. The structure is identical to the Get Proposal response.Unique numeric ID of the proposal.
ISO 8601 timestamp reflecting the update just performed.
Full financial breakdown. See Get Proposal for field details.
Error Codes
| Code | Meaning |
|---|---|
| 401 | Not authorized. Check that your HMAC signature and headers are correct. |
| 402 | The account’s subscription is inactive or expired. |
| 403 | Your user does not have permission to update this proposal. |
| 404 | No proposal found with the given ProposalId. |
| 409 | The proposal’s current state prevents editing (e.g. terminal status). |