Update a draft order's contact details
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Headers
A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.
Path Parameters
Body
CONTACT ONLY, and send at least one of the two. Everything else on a draft is computed (the money fields), stamped (status, completed_order_id, the timestamps) or fixed at create (currency_code), and each is refused by name with the reason. THREE STATES PER FIELD. An omitted key leaves the column alone, an explicit null CLEARS it, and a string sets it. An empty string is a 400: null means "not captured" on the way out, and a body that could send "" as a clear would make the two the same request. Open drafts only. A completed draft answers 409 draft_not_open, because rewriting the buyer on the quote behind a placed order would leave the two disagreeing with nothing recording that they ever did.
Response
Success
