There are some mismatches between the documented datatypes/-structure of the REST API and the implemented ones.

ImageList¶

• Name (non-empty in API, but not in doamin)

Image¶

• Relative path (non-empty in API, but not in doamin)
• Sort order (>=1 in API, but not in domain)

ImageTitle¶

• Text (non-empty in API, but not in domain)

ImageAltTitle¶

• Text (non-empty in API, but not in domain)

Option¶

• Sort order (>=1 in API, but not in domain)

Value¶

• Sort order (>=1 in API, but not in domain)
• Model number (non-empty in API, but not in doamin)

Product Option¶

• ID (>=1 in domain, but not in API)
• Option ID (>=1 in domain, but not in API)
• Option value ID (>=1 in domain, but not in API)
• Image list ID (>=1 in domain, but not in API)
• Product ID (In domain needed, but should not be part of the API response body!)
• Sort order (>=1 in API, but not in domain)

Product Variant¶

• ID (>=1 in domain, but not in API)
• Option ID (>=1 in domain, but not in API)
• Option value ID (>=1 in domain, but not in API)
• Product ID (In domain needed, but should not be part of the API response body!)
• Sort order (>=1 in API, but not in domain)
• Model number (non-empty in API, but not in doamin)
• GTIN (non-empty in API, but not in doamin)
• ASIN (non-empty in API, but not in doamin)
• EAN (non-empty in API, but not in domain)

Note: In we agreed that in general, a sort order must not be >=1 so that an update of the API documentation is needed here.