Update a bundle's title, price, currency or status
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
PATCH rather than PUT, and the method is the contract: an omitted key keeps its stored value, so a client that computed a partial body cannot blank the merchant's title or reset the price to zero and read a 200 as agreement. The same four keys the create accepts are writable here, because a field that can be set once and never corrected is worse than one never published: the only remaining fix would be delete-and-recreate, and this family publishes no delete. A PATCH THAT ONLY MOVES price_minor CHANGES WHAT EVERY COMPONENT IS WORTH PER UNIT AT CHECKOUT, because the bundle carries one authoritative set price and the cart spreads it across whatever components exist. That is the intended use of this route rather than a hazard, and it is worth knowing when reading an audit trail: nothing about the components changed. AN EMPTY PATCH IS A 400, not a no-op. This resource publishes updated_at as the incremental-sync key, so a bumped timestamp on a request that changed nothing tells every polling client to re-pull for nothing. IT DOES NOT TOUCH COMPONENTS, and items is refused BY NAME because the read EMBEDS the array and the first instinct is to send it back with one element changed. Accepting that would be a whole-array replace: any component left out would be removed, and because the set price is allocated across whatever remains, the survivors would each silently become worth MORE per unit. A client that dropped one element by accident would reprice the rest and get a 200 for it. IT CONVERGES. Every accepted value is absolute rather than a delta, so replaying the same body with a fresh key past the idempotency window lands the same bundle in the same state. No money and no stock move, and nothing is emitted: this family registers no webhook topics. THE RESPONSE IS THE WHOLE BUNDLE, components included, read in the same transaction as the merge, so it is byte-identical to GET /api/v1/bundles/{bundleId} rather than a fragment. component_sum, price, available_quantity, in_stock, unlimited and the provenance keys (id, store_id, created_at, updated_at) are refused for the create's reasons. No key may be null: nothing here is nullable, so null cannot mean "clear it" and is a 400 naming the field. A bundle id that resolves to nothing in this store is a generic 404.
Truncated at 200 bytes, as on the create. Present but blank or whitespace is a 400 naming the key rather than a stored empty title: omit the key to leave it unchanged.
The set price in INTEGER MINOR UNITS of the bundle's currency. Absolute, never a delta, and re-divided across the components at the next cart recompute.
0 <= x <= 1000000000000Stored lowercase and validated against the ISO 4217 catalogue. Present but blank is a 400. Re-denominating a bundle does NOT convert price_minor: the same integer is then read in the new currency's minor units, so send both keys together when you mean to move markets.
disabled withdraws the bundle from sale and keeps every component, which is this family's reversible stand-in for a delete. active puts it back.
active, disabled Response
Success