v1.032

Re-syncing an order now applies a corrected item price and corrected B2B attributes.
Until now Create or Update Order (POST /v1/integrations/order) only carried quantity, packing group, special instructions and lot requirements onto an item that already existed on the order. A changed price or changed b2b_attributes on that item were accepted with a 200 and then silently dropped, so a correction sent from your side never reached the order. Both fields are applied now and the order total is recalculated with them.

🚀 New Endpoints

None

🛠 Schema & Property Updates

None

📦 New Support Schemas

None

📖 Documentation & Constraints Changes

• Create or Update Order (POST /v1/integrations/order) — items[].price is no longer immutable. Sending it again for an item that already exists on the order updates the stored price, and the order total is recalculated from it. Omitting the field leaves the stored price unchanged, so a price cannot be cleared through this endpoint.
• Create or Update Order (POST /v1/integrations/order) — items[].b2b_attributes is no longer immutable. Attributes present in the payload are created or updated by name on an item that already exists; attributes you do not send are left untouched and are never removed.

No endpoints, fields, or required-status were removed or changed. Two fields that were documented as immutable are now applied on update, which is what a client sending them already expects, so this version stays fully backward-compatible. Items are only updated while the order is still editable and has not been edited manually in the ShipMonk app — that was already the case and has not changed.