Bulk Update Deals
POST /deals/bulk
Apply ONE change to up to 100 deals.
PUT semantics on every field of change: null leaves a value alone, an
EMPTY STRING clears it. Omitting a field and sending "" are therefore
different instructions and the second one is destructive.
Read the per-deal result rather than the HTTP status: a deal the caller cannot write is reported, not fatal.
Authorizations
Parameters
Header Parameters
Request Body required
Apply one change to up to 100 deals.
Each deal is checked against the caller’s deal scope individually; one the caller cannot write is reported rather than aborting the batch.
object
The change applied to EVERY deal in the batch.
PUT semantics, and the distinction matters: null leaves a value alone,
an EMPTY STRING clears it. So omitting a field and sending "" are
different instructions, and the second one is destructive.
object
Responses
200
Successful Response
object
An open envelope for a deal, a merge preview or a column result.
Open because the crossfire and merge-preview payloads are computed shapes that grow with the product, and a closed model would drop a field from an ADVISORY read - where a missing signal reads as “nothing to worry about” rather than “we did not tell you”.
object
422
Validation Error