Approve or reject a demand exchange revision
Approve or reject a revision awaiting approval. Approving requires a decider distinct from the revision’s own composer (maker-checker, enforced here and by a table constraint); rejecting — including the composer withdrawing their own submission — has no such restriction, because it creates no buyer-visible evidence. An approved decision captures the revision as a real pass on the exchange’s compose run in the same transaction. Scoped to the caller’s storefront.
Authorizations
API key or access token
Path Parameters
1 <= x <= 90071992547409911 <= x <= 9007199254740991Body
Approve or reject a revision awaiting approval. expectedSubmissionGeneration must match the revision's current submissionGeneration (as read) — a stale generation is refused rather than applied to a since-changed submission. Approving requires a decider distinct from the revision's composer (maker-checker); rejecting — including the composer withdrawing their own submission — has no such restriction because it creates no buyer-visible evidence.
Response
Approve or reject a demand exchange revision
A seller-composed adjustment to a live demand exchange: silent while draft or awaiting approval, and a real pass on the exchange's compose run once sent.
draft, awaiting_approval, sent, discarded ok, error The merchandising engine's own error, kept mounted (with the seller's declared overrides) when composition failed, rather than the sheet being torn down.
The draft response envelope, in the same shape the canonical proposal card already renders (redacted). Null when compose failed.
The draft product snapshots keyed by product id, paired with proposalPreview so the canonical proposal card renders a draft with no builder-specific projection. Null when compose failed.
Read once from the persisted brief request at compose time. A draft never converts into these or issues a rate hold — that is the buyer-facing response path's job, not a discardable draft's.
-9007199254740991 <= x <= 9007199254740991How a sent revision cleared. Null until sent. An auto send never carries a human decision record.
Truthful buyer-visibility (build-5 ruling): null until sent. A sent revision always reports not_delivered/no_delivery_lane today — investigation found no seller-to-buyer lane for a subsequent proposal and no honest staging lane either. The UI states the buyer's agent was not notified; it never claims a notification that did not happen.
False when the caller is this revision's own composer (maker-checker) or the revision is not awaiting approval.
True for a draft (fresh or bounced back after rejection) composed by the caller; false once submitted, sent, or discarded, or when a different storefront user composed it.
True when the caller composed this draft, it hasn't been submitted, sent, or discarded, and its last compose succeeded. A draft whose compose failed can only be discarded or re-composed via amend.
True for a draft (fresh or bounced back after rejection) composed by the caller; false once submitted, sent, or discarded, or when a different storefront user composed it.
Bumped on every submit, resubmit, and amend. A decision must be made against this exact value or it is refused as stale.
-9007199254740991 <= x <= 9007199254740991How many times this row has been amended in place. Counts toward the lifetime adjustment cap alongside the row itself.
-9007199254740991 <= x <= 9007199254740991