Skip to main content

Product Listings

📄️Export Draft Template Fields

Download the draft category's field requirements as a styled Excel (.xlsx) workbook. The workbook has one row per channel field with its priority (required / recommended / optional), type, allowed values, plain-language guidance, what SKU.io currently maps into it, and the resolved sample value — so the still-empty fields can be collected from a supplier. Required fields lead the sheet; fixed-option fields get a dropdown of the allowed values on the sample cell.

📄️Apply Content Change Group

Applies every open change in one bucket in the background, without listing ids. The bucket is described by the same filters used to list it, so a bucket of several thousand listings needs no enumeration by the caller. Send the filters in the QUERY STRING — filters in the request body are ignored, which would silently widen the apply. The apply must be scoped by at least one of filter[field], filter[field_group], or filter[integration_instance_ids]; an unscoped call returns 422. High-impact fields such as product name are rejected with 422 and must be applied one listing at a time. Very large buckets are applied in passes: listings_queued below listings_total means the call should be repeated to continue. Follow progress with the returned tracked_job_log_id.