Refresh Proposal Item Costs
Pricing
Refresh Proposal Item Costs
POST /public/proposals//items/costupdate — Re-reads supplier costs for every item in a proposal from the catalog. Takes no request body.
POST
Refresh Proposal Item Costs
Re-reads catalog data for the proposal’s
Where margin is set as a percentage of cost, refreshed costs move those prices too — see reading proposal items.
Part items. Use it after supplier pricing changes upstream and the proposal has gone stale — the per-item costUpdateDate tells you how old the numbers are.
For each part it re-reads the supplier cost, the in-stock flag, and the MSRP. Where the part’s supplier is set to use a future cost, that is the figure applied. An item with no supplier assigned picks up the part’s default supplier and its cost.
Items carrying a hand-entered amount are skipped outright — the refresh leaves their cost, stock flag, and MSRP exactly as they are. An item is marked that way as soon as a cost or an MSRP is written on it, including through update cost and update MSRP, so refreshing will never overwrite a price your integration set on purpose.
Costs are also only re-read for suppliers whose pricing your account is allowed to see. Where it is not, the cost and costUpdateDate are left unchanged — but the item is not skipped the way a hand-entered one is: its in-stock flag is still cleared and its MSRP is still refreshed from the catalog.
Labor, CustomItem, and Fee items are not touched, and neither are sell prices. The proposal id goes in the path and the request takes no body. This is proposal-wide: there is no per-item variant and no way to limit it to one area option.
Success is an empty
200 or 204. Along with delete items, this is one of two item endpoints with no response body, so call get proposal afterwards to read the new values.Authorizations
Portal application identifier used as part of HMAC-authenticated API requests.
Portal user API key used together with the HMAC signature headers.
Timestamp header included in the signed request to prevent replay attacks.
HMAC-SHA256 signature for the request, calculated over the canonical string defined in the authentication docs.
Headers
Accept Header
Available options:
application/json Path Parameters
Unique ID of the proposal (not the proposal number).
Body
application/json
Proposals Service
Response
Success