VIN

The parts-ordering card for a VIN.

What a parts counter asks for, one line each, and where each line came from: the decode, the catalog engine when the decode settles it, the emission standard when EPA's file was matched to that engine, and the build dates a recall campaign names for the model year. A build-date line is the range a campaign covers, not this vehicle's build date. text is the card as plain text, ready to paste. Works without shop data: the lines that need it are then left off.

get/v1/vin/{vin}/parts-card

Request

  • Base URL: https://open.wenmarpro.com
  • URL: https://open.wenmarpro.com/v1/vin/{vin}/parts-card
  • Auth: none declared

Path parameters

vinstring required

A 17-character VIN.

Query parameters

yearinteger

The model year, when the VIN's tenth character leaves two possible.

Response

The card.

attributionstring[] required
engine_settledboolean required

Whether the decode settled one catalog engine. The catalog engine and emission standard lines are there only when it did.

textstring required

The lines as plain text, one Label: value each.

vinstring required

Example response

{
  "lines": [
    {
      "label": "Engine",
      "source": "VIN decode (NHTSA vPIC)",
      "value": "2.0L"
    }
  ],
  "vehicle": {
    "id": "2018_ford_f-150",
    "make": "Ford",
    "model": "F-150"
  },
  "warnings": [
    {
      "code": "invalid_check_digit"
    }
  ]
}

Changes

No recorded changes to this operation across all 1 revision of this API.