WebApi

<back to all web services

VinDecodeEquipmentRequest

The following routes are available for this service:
GET/vindecode/{VIN}/styles/{StyleId}/equipmentGet Equipment for a VIN and StyleId.
OPTIONS/vindecode/{VIN}/styles/{StyleId}/equipment

To override the Content-type in your clients HTTP Accept Header, append the .xml suffix or ?format=xml

HTTP + XML

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /xml/reply/VinDecodeEquipmentRequest HTTP/1.1 
Host: api.homenetiol.com 
Content-Type: application/xml
Content-Length: length

<VinDecodeEquipmentRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/HNI.InventoryOnline.WebIOL.WebApi.MessageHandlers.Mobile">
  <StyleId xmlns="http://schemas.datacontract.org/2004/07/HNI.InventoryOnline.WebIOL.WebApi.Common.Messages.Mobile">String</StyleId>
  <Vin xmlns="http://schemas.datacontract.org/2004/07/HNI.InventoryOnline.WebIOL.WebApi.Common.Messages.Mobile">String</Vin>
</VinDecodeEquipmentRequest>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<VinDecodeEquipmentResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/HNI.InventoryOnline.WebIOL.WebApi.Common.Messages.Mobile">
  <Equipment>
    <OptionalEquipment>
      <OptionalEquipment>
        <Description>String</Description>
        <EquipmentIdentifier>String</EquipmentIdentifier>
        <OptionCode>String</OptionCode>
      </OptionalEquipment>
    </OptionalEquipment>
    <StandardEquipment>
      <StandardEquipment>
        <Category />
        <Description>String</Description>
        <EquipmentIdentifier>String</EquipmentIdentifier>
      </StandardEquipment>
    </StandardEquipment>
  </Equipment>
</VinDecodeEquipmentResponse>