Parts compatibility is supported in select Parts & Accessories categories only for the following marketplaces:

  • eBay US Motors (100)
  • Canada (2)
  • UK (3)
  • Australia (15)
  • Germany (77)

Within those marketplaces, parts compatibility is supported in select Parts & Accessories leaf categories. Use the REST-based getAutomotivePartsCompatibilityPolicies method to determine whether a specific leaf category supports parts compatibility and whether compatibility for that category is based on assemblies or specifications. If the target leaf category is returned in the response, that category supports parts compatibility.

Check individual leaf categories

To determine whether a specific leaf category supports parts compatibility, call getAutomotivePartsCompatibilityPolicies for the marketplace and use the optional filter=categoryIds:{...} query parameter to limit the response to the category or categories you want to check.

Inspect these fields in the response:

  • automotivePartsCompatibilityPolicies.categoryId — identifies the returned category.
  • automotivePartsCompatibilityPolicies.compatibilityBasedOn — indicates whether compatibility is based on ASSEMBLY or SPECIFICATIONS.
  • automotivePartsCompatibilityPolicies.compatibleVehicleTypes — identifies the vehicle types supported for compatibility.

Sample request for an individual category 

GET /sell/metadata/v1/marketplace/EBAY_US/get_automotive_parts_compatibility_policies?filter=categoryIds:{33709}

Fields to look for in the response 

{
  "automotivePartsCompatibilityPolicies": [
    {
      "categoryId": "33709",
      "compatibilityBasedOn": "ASSEMBLY",
      "compatibleVehicleTypes": [
        "CAR_AND_TRUCK"
      ]
    }
  ]
}

If the requested leaf category is returned in the response, that category supports parts compatibility. Use compatibilityBasedOn to determine whether compatibility is managed by application/assembly data or by specification data.

Identify all categories that support parts compatibility

To identify all leaf categories in a marketplace that support parts compatibility, call getAutomotivePartsCompatibilityPolicies without the category filter. Review the returned category entries and their compatibility metadata.

Sample request for all supported categories 

GET /sell/metadata/v1/marketplace/EBAY_US/get_automotive_parts_compatibility_policies

Fields to look for in the response 

{
  "automotivePartsCompatibilityPolicies": [
    {
      "categoryId": "33709",
      "compatibilityBasedOn": "ASSEMBLY",
      "compatibleVehicleTypes": [
        "CAR_AND_TRUCK"
      ]
    },
    {
      "categoryId": "6028",
      "compatibilityBasedOn": "SPECIFICATIONS",
      "compatibleVehicleTypes": [
        "MOTORCYCLE"
      ]
    }
  ]
}

Check minimum and maximum compatibility values

Use the REST-based getMotorsListingPolicies method to determine the minimum required and maximum allowed compatibility entries for categories that support compatibility by application or assembly.

Inspect these fields in the response:

  • motorsListingPolicies.categoryId — identifies the returned category.
  • motorsListingPolicies.minItemCompatibility — indicates the minimum number of compatibility entries required for the category.
  • motorsListingPolicies.maxItemCompatibility — indicates the maximum number of compatibility entries allowed for the category.

Sample request for compatibility limits 

GET /sell/metadata/v1/marketplace/EBAY_US/get_motors_listing_policies?filter=categoryIds:{33709}

Fields to look for in the response 

{
  "motorsListingPolicies": [
    {
      "categoryId": "33709",
      "minItemCompatibility": 0,
      "maxItemCompatibility": 41
    }
  ]
}

Check compatibility by specification

If compatibilityBasedOn is SPECIFICATIONS, use the Taxonomy API method getItemAspectsForCategory to determine which item specifics apply to the leaf category and whether each one is required, recommended, or optional.

Inspect these fields in the response:

  • aspects.localizedAspectName — identifies the returned aspect.
  • aspects.aspectConstraint.aspectRequired — indicates whether the aspect is required.
  • aspects.aspectConstraint.aspectUsage — indicates whether a non-required aspect is recommended or optional.

Sample request for by-specification categories 

GET /commerce/taxonomy/v1/category_tree/{category_tree_id}/get_item_aspects_for_category?category_id=6028

Fields to look for in the response 

{
  "aspects": [
    {
      "localizedAspectName": "Make",
      "aspectConstraint": {
        "aspectRequired": true,
        "aspectUsage": "RECOMMENDED"
      }
    },
    {
      "localizedAspectName": "Model",
      "aspectConstraint": {
        "aspectRequired": false,
        "aspectUsage": "RECOMMENDED"
      }
    }
  ]
}