VehiclePartLookup

Description

Given a car part, VehiclePartLookup returns the vehicle models and years the part works in. For example, one carburetor might work in the same vehicle model over a five year period.

You can page through the parts returned using the parameters, Count and FitmentPage. For more information, see Paging Through Fitments.

Availability

US locale.

Request Parameters

Name	Description	Required
BedId	Identifier that uniquely identifies the bed style of a truck. This parameter does not pertain to cars. Type: nonNegativeInteger Default: None Valid Values: A valid ID Constraint: None	No
`BodyStyleId`	Identifier that uniquely identifies the body style of the car. Type: nonNegativeInteger Default: None Valid Values: A valid ID Constraint: None	No
`BrakesId`	Identifier that uniquely identifies the brake type on a car. Type: nonNegativeInteger Default: None Valid Values: A valid ID Constraint: None	No
`DriveTypeId`	Identifier that uniquely identifies the type of drive on the car. A drive type, for example, is four wheel drive. Type: nonNegativeInteger Default: None Valid Values: A valid ID Constraint: None	No
`EngineId`	Identifier that uniquely identifies the type of engine in the car. An engine type would be, for example, the piston displacement, like 409 cu. inches. Type: nonNegativeInteger Default: None Valid Values: A valid ID Constraint: None	No
`FitmentCount`	Specifies the number of Fitments returned per page of results. Fitments are a combination of car characteristics, including make, model, year, and trim. This parameter is only used with the Fitments response group. See `FitmentPage`. Type: Integer Default: 25 Valid Values: 1 - 200 Constraint: None	No
`FitmentPage`	The page number of the Fitments returned. Use `FitmentPage` with `Count` to page through the results. Type: Integer Default: 1 Valid Values: A valid ID Constraint: None	No
`IdType`	Specifies the type of ID. Type: String Default: ASIN Valid Values: ASIN	No
`MakeId`	Identifier that uniquely identifies the make of the car. Type: nonNegativeInteger Default: None Valid Values: A valid ID Constraint: Required when using the VehiclePartFit response group	Constraint
`MfrBodyCodeId`	Identifier that uniquely identifies the manufacturer's car body code. Type: nonNegativeInteger Default: None Valid Values: A valid ID Constraint: None	No
`ModelId`	Identifier that uniquely identifies the model of the car. Type: nonNegativeInteger Default: None Valid Values: A valid ID Constraint: Required when using the VehiclePartFit response group	Constraint
`SpringTypesId`	Identifier that uniquely identifies the type of spring shocks in the car. Type: nonNegativeInteger Default: None Valid Values: A valid ID Constraint: None	No
`SteeringId`	Identifier that uniquely identifies the steering type of the car. A steering type would be power steering. Type: nonNegativeInteger Default: None Valid Values: A valid ID Constraint: None	No
`TransmissionId`	Identifier that uniquely identifies the transmission type used in the car. Type: nonNegativeInteger Default: None Valid Values: A valid ID Constraint: None	No
`TrimId`	Identifier that uniquely identifies the trim on the car. Trim generally refers to a package of car options, for example, Volvo GL versus Volvo DL. Using this parameter helps narrow responses. Type: nonNegativeInteger Default: None Valid Values: A valid ID	No
`WheelbaseId`	Identifier that uniquely identifies the car's wheelbase. Type: nonNegativeInteger Default: None Valid Values: A valid ID Constraint: None	No
`Year`	The year of the vehicle. Type: String Default: None Valid Values: A four-digit year, which is returned by `VehicleSearch` Constraint: Required when using the VehiclePartFit response group	Constraint
`ResponseGroup`	Specifies the types of values to return. You can specify multiple response groups in one request by separating them with commas. Type: String Default: HasPartCompatibility Valid Values: Fitments \| HasPartCompatibility \| VehiclePartFit	No

VehiclePartLookup also accepts the parameters that all operations can use. For more information, see, Common Request Parameters

Examples

Look up a vehicle part specified by an ItemId.

http://ecs.amazonaws.com/onca/xml?
Service=AWSECommerceService&
AWSAccessKeyId=[AWS Access Key ID]&
ItemId=[ItemId]&
Operation=VehiclePartLookup

The response to this request is shown in, Response to Sample Request.

Sample Response

The following XML is a snippet of the full response to the first sample request.

<Part>
  <Item>
    <ASIN>B00064P99W</ASIN>
  </Item>
  <HasPartCompatibility>1</HasPartCompatibility>
  <VehiclePartFit>
    <IsFit>MAYBE</IsFit>
    <MissingVehicleAttributes>
      <ParameterName>TrimId</ParameterName>
    </MissingVehicleAttributes>
  </VehiclePartFit>
</Part>
<MissingVehicleAttributes>
  <ParameterName>EngineId</ParameterName>
  <ParameterName>TrimId</ParameterName>
</MissingVehicleAttributes>
<PartBrowseNodeBins>
  <Bin>
    <BinName>Exterior Accessories</BinName>
    <BinItemCount>55</BinItemCount>
    <BinParameter>
      <Name>BrowseNodeId</Name>
      <Value>15857511</Value>
    </BinParameter>
  </Bin>
  <Bin>
    <BinName>Interior Accessories</BinName>
    <BinItemCount>89</BinItemCount>
    <BinParameter>
      <Name>BrowseNodeId</Name>
      <Value>15857501</Value>
    </BinParameter>
  </Bin>
  <Bin>
    <BinName>Oils & Fluids</BinName>
    <BinItemCount>8</BinItemCount>
    <BinParameter>
      <Name>BrowseNodeId</Name>
      <Value>15718791</Value>
    </BinParameter>
  </Bin>
  <Bin>
    <BinName>Paint, Body & Trim</BinName>
    <BinItemCount>40</BinItemCount>
    <BinParameter>
      <Name>BrowseNodeId</Name>
      <Value>15709231</Value>
    </BinParameter>
  </Bin>
<PartBrowseNodeBins>