Update Listing Content Rules
PUT/api/product-listings/:productListing/content-sync-rules
Customise the content ownership rules for a single product listing, overriding what its sales channel says.
Send only what should differ from the channel: groups keyed by field group and fields keyed by field name, each holding an owner and an optional auto_apply. Anything left out keeps following the channel, so a later change to the channel's defaults still flows through to it.
Both groups and fields are required keys — send them as empty objects to clear every customisation and put the listing back on the channel defaults.
Field-level entries beat group-level entries, and anything set here beats the channel.
Group keys: identity, descriptive, media, physical. Field keys: barcode, mpn, name, brand, attributes, images, weight, dimensions.
Ownership values: catalog (channel edits are flagged only), channel (channel edits can be pulled into the catalog), two_way (both sides may edit; simultaneous edits become conflicts).
Unknown group keys, unknown field keys, and unknown ownership values are rejected with a 422.
The full resolved rule set is returned, exactly as the GET returns it.
Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.