Follows RFC 7396 JSON Merge Patch rules, but send the body as application/json: a body sent as application/merge-patch+json returns 415. The update propagates in real time. status accepts active, paused, archived or scheduled; the other statuses are produced by the buyers and are read-only. The status is written to each buyer on the deal in turn, after the other fields in the request are applied, so a failure partway can leave the buyers in different states: re-send the same request until it returns 200. An archived deal refuses every edit with a 502, so re-sending will not help; if the request was archiving the deal, read the deal to see whether the archive landed. On an open deal with no DSP the status is set on the deal itself, after the other fields, and a scheduled one refuses paused with a 502, which re-sending will not help either. The 200 reports the status the deal resolved to rather than the one sent; see the Deal lifecycle guide. A deal whose buyers are all on a DSP that manages deal status through its own integration rejects status with 400: dv360 on any deal, and thetradedesk on a pmp deal once Sovrn turns on The Trade Desk's integration; a thetradedesk buyer on an open deal stays settable. Read statusSettable on the deal before offering a status change at all: it is false whenever any buyer is on such a DSP, which is broader than the 400, because a deal that mixes one with other buyers accepts status and need not resolve to the value you sent. On a deal with a dv360 buyer the DV360 field requirements apply to the merged result, adFormat cannot be changed, environments cannot include dooh, and environments can change only within the deal's DV360 medium type (DV360 fixes the format and the medium type at creation). An edit that adds a dv360 buyer is held to the DV360 field requirements too, so the deal it leaves cannot include dooh in environments. On an open deal, buyers replaces the deal's DSPs: each buyer carries no seats, each DSP is named once (BidSwitch buyers become one bidswitch), a DSP left out stops receiving the deal, an empty buyers leaves the deal with no DSP, and dv360 cannot be added back to a deal it was removed from. On a pmp deal buyers names at least one buyer, every buyer carries seats and bidswitch is refused. A buyer added to a paused deal is added paused, so a deal that still reads statusSettable: true stays paused. On a pmp deal with a thetradedesk buyer, an edit that sends schedule.startDate, schedule.endDate or buyers must leave the deal with an end date before the same calendar date 2 years after its start, an edit that adds a thetradedesk buyer included; any other edit is not held to it. Once the thetradedesk buyer has accepted a pmp deal, and while The Trade Desk's integration is on, an edit cannot change that buyer's first seat, the start date from its own day on or an end date that has passed, and cannot set an end date in the past (see the Trade Desk buyers section).