Open a draft order
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.
Body
Creates an EMPTY quote. Lines are added one at a time by POST /api/v1/draft-orders/{draftOrderId}/items, so each is priced from the catalogue rather than from a body, and there is deliberately no items array here. id, status, subtotal_minor, total_minor, completed_order_id, items, store_id and the timestamps are refused BY NAME rather than ignored, so a client that sent status "completed" is told instead of reading a 201 as a converted quote.
REQUIRED, and there is no store default to fall back on. The two money fields are stored in it and it cannot be changed afterwards, so a guessed currency would permanently mislabel an outstanding offer. Any 3-letter code, matched case-insensitively and served back lowercase.
The buyer's address. Optional here and settable later. A draft cannot be completed without one, so its presence is the readiness signal.
An opaque reference into /api/v1/customers. No foreign key validates it, so an unknown id is accepted exactly as the dashboard accepts one.
Response
Created
