Same rules as bulkupdate, for a single product object. Only reference is required.
Empty values
A field sent as null is treated as absent and left unchanged, except noveltyAlertDate and preorder_date (see below).
How to clear a value:
| Field | Send | Effect |
|---|---|---|
subtitle, description, model | "" | Empties the field |
discountedprice | 0 | Removes the discounted price |
discountbegin + discountend | "@0" for both | Removes the discount period |
label1.id / label2.id | 0 | Removes the label |
label1 / label2 begin + end | "@0" for both | Removes the label period |
noveltyAlertDate, preorder_date | null | Disables novelty / pre-order |
eligible_carriers, cms_page, cross_sells, gammes | [] | Removes every link |
attributes | value_code suffixed with -delete | Unlinks that attribute value ([] removes nothing) |
Rejected when empty ("", or [] / {} for collections): title, site, season, department, collection, width, height, length, weight, provider, type, brand, carrier, noveltyAlertDate, preorder_date, gallery, parcel, inventory, pricing_matrix, association, translations (and any empty string inside a translation), batch_contents for a batch type.
Do not send an empty string to a numeric or 0/1 field (price, buyingprice, ecotax, packing, visible, dispo_mag, click_and_collect, click_and_go, e_reservation, backInStock, allowed_relay_point, allowed_restocking, unlimited_stock, return_paid, ship_from_store, flag_redirection, robot_index, robot_follow, fdp_offert): it is currently stored as 0 / non (e.g. visible: "" hides the product, buyingprice: "" sets the selling price to 0). Send the explicit value instead, or omit the field. Likewise an empty discountbegin, discountend or label begin / end is stored as the current date, not cleared.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||