Update a price list
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
Every value is an absolute target, so replaying converges. Setting status to disabled removes the list from resolution completely and immediately, and destroys nothing: it is the reversible operation published in place of a list delete, which would cascade this list's prices and its customer-group targeting with no restore.
Required on create.
Required on create. A list price applies only when it is strictly BELOW the variant's base price, on both types: a price INCREASE pushed through an "override" list answers 200 and changes nothing at checkout.
sale, override Defaults to disabled on create, so a public create cannot put pricing in front of shoppers without a second deliberate act. Flipping to active takes effect at the next cart recompute: resolution happens at read time and is never snapshotted, so carts already in flight re-price.
active, disabled Merchant notes. Never shown to a shopper.
2000Response
Success
