Skip to main content

List Listing Profile Mappings

GET 

/api/v2/sales-channels/:salesChannel/listing-profiles/:profile/mappings

The general field mappings a listing profile carries — the mappings that hold whatever the category, so a category template does not have to repeat them.

Required scope: products:read

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

A profile's vocabulary is the channel's CORE listing fields and nothing else — the fields the channel asks for on every listing whatever the category, as its module declares them. Category aspects are never returned and can never be stored here: a template is category-specific, a profile is not. A row with is_core: false is a mapping made before that rule was enforced — it is still live, so it is returned to be removed rather than hidden.

Each row carries EITHER the profile's own binding in source_type / source_value, or — when the profile leaves the field unbound — what it would resolve to from a lower layer in inherited_source_type / inherited_source_value / inherited_from (channel or integration). Exactly one of the two pairs is populated.

source_type is one of product_field, product_attribute, static, expression. is_core marks a listing-level field the channel always needs; category_count is how many synced categories carry the field (0 for core fields).

A field's value resolves most-specific-first: per-listing override, then category template, then this profile, then the channel-wide mappings, then the integration-wide defaults.

Returns 404 when the profile does not belong to the sales channel in the path.

Authentication: Requires Bearer token.

Request

Responses

OK

Response Headers
    Content-Type