| compatibilityProperties |
\ld\php\sdkEbayInventory\Model\NameValueList[] |
This container consists of an array of motor vehicles that are compatible with the motor vehicle part or accessory specified by the SKU value in the call URI. Each motor vehicle is defined through a separate set of name/value pairs. In the <strong>name</strong> field, the vehicle aspect (such as 'make', 'model', 'year', 'trim', or 'engine') will be identified, and the <strong>value</strong> field will be used to identify the value of each aspect. The <a href="/api-docs/commerce/taxonomy/resources/category_tree/methods/getCompatibilityProperties">getCompatibilityProperties</a> method of the Taxonomy API can be used to retrieve applicable vehicle aspect names for a specified category, and the <a href="/api-docs/commerce/taxonomy/resources/category_tree/methods/getCompatibilityPropertyValues">getCompatibilityPropertyValues</a> method of the Taxonomy API can be used to retrieve possible values for these same vehicle aspect names. Below is an example of identifying one motor vehicle using the <strong>compatibilityProperties</strong> container:<br><br><code>"compatibilityProperties" : [<br> {<br> "name" : "make",<br> "value" : "Subaru"<br> },<br> {<br> "name" : "model",<br> "value" : "GL"<br> },<br> {<br> "name" : "year",<br> "value" : "1983"<br> },<br> {<br> "name" : "trim",<br> "value" : "Base Wagon 4-Door"<br> },<br> {<br> "name" : "engine",<br> "value" : "1.8L Turbocharged"<br> }<br>]</code><br><br>Typically, the make, model, and year of the motor vehicle are always required, with the trim and engine being necessary sometimes, but it will be dependent on the part or accessory, and on the vehicle class.<br/><br/><span class="tablenote"> <strong>Note:</strong> The <strong>productFamilyProperties</strong> container is in the process of being deprecated and will no longer be supported in February of 2021, so if you are a new user of <strong>createOrReplaceProductCompatibility</strong>, you should use the <strong>compatibilityProperties</strong> container instead, and if you are already integrated and using the <strong>productFamilyProperties</strong> container, you should make plans to migrate to <strong>compatibilityProperties</strong>. The <strong>productFamilyProperties</strong> and <strong>compatibilityProperties</strong> containers may not be used together or the call will fail.</span> |
[optional] |