Attribute values

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL


        
          
            https://content.doc.winkelstraat.nl/mcp

Standard setup for AI tools providing an mcp.json file

{
  "Content API MCP server": {
    "url": "https://content.doc.winkelstraat.nl/mcp"
  }
}

Product information is sent in values. Every attribute is a list containing one object with data and locale:

"values": {
  "manufacturer": [ { "data": "guess", "locale": null } ],
  "name": [
    { "data": "Summer top", "locale": "en_US" },
    { "data": "Zomer top", "locale": "nl_NL" }
  ]
}

locale is only used by text attributes that can be translated (name, description, fit, material). Use nl_NL or en_US. When you send "locale": null for such an attribute, the value is used for every language. For all other attributes use "locale": null.
scope is not used and may be left out.
An empty string is treated as "no value".

Allowed values must match Winkelstraat values

For attributes with a fixed list of values, such as brand (manufacturer), colour (color), size (size), season (season) and condition (condition_type), you must send the code of a value that Winkelstraat supports. Your own names are not translated: Guess matches the code guess (codes are compared in lower case), but Guess Jeans does not.

Look up the allowed codes with GET /api/rest/v1/retailer/attributes/{code}/options, for example /api/rest/v1/retailer/attributes/color/options. Use GET /api/rest/v1/retailer/attributes to see which attributes exist and which type they have. Attributes of type pim_catalog_simpleselect or pim_catalog_multiselect have a list of allowed values.

Categories work the same way: use GET /api/rest/v1/retailer/categories/codes to find the category code to send in category.

A brand must also be activated for the Content API by Winkelstraat. If you send a brand code from the option list and still receive The manufacturer value <brand> is not supported/disabled, contact partnersuccess@winkelstraat.nl.

Common value errors

Message	Meaning and solution
`The manufacturer value <value> is not supported/disabled`	The brand is unknown or not active. Check the code in `/attributes/manufacturer/options`, or contact Partner Success.
`The color value <value> is not supported/disabled`	Use a code from `/attributes/color/options`.
`The size with value '<value>' is not supported/disabled`	Use a code from `/attributes/size/options`.
`The manufacturer value <value> differs from manufacturer product value <value>`	All sizes of a product group must have the same brand.
`Invalid category code "<code>"`	Use a code from `/categories/codes`.
`category attribute is missing for <identifier>`	The `category` field is missing.
`Required value "<attribute>" is not set for product "<identifier>"`	A required value is missing when creating a product (see the create endpoint).
`Missing required value for product attribute manufacturer_product_number for product "<identifier>"`	Send `manufacturer_product_number`.
`Unknown attribute "<attribute>" for product "<identifier>"`	The attribute code does not exist. Check `GET /attributes`.
`Attribute '<attribute>' contains unsupported HTML tags`	Remove HTML tags that are not allowed from `name`, `description` and similar text values.
`EAN is required and cannot be empty.`	This brand requires an EAN for every product.
`EAN must be unique.`	Another one of your products already uses this EAN.

In error messages the identifier can be shown with your partner code in front of it (for example wsnl123-TSHIRT-001-BLACK-M). It refers to your own identifier.