Vehicle identity and specifications
What identity and factory specifications decode from this vehicle identifier?
The data that answers it
Ranked by fit · best firstThe CarsXE Lien & Theft response decodes a supplied VIN to year, make, model, and body class while also reporting theft-event classifications. This is a bounded identity/specification decode; the cited documentation does not expose decoder/database version, verification timestamp, GVWR, trim, engine, or other broader factory specifications.
CarsXE's VIN endpoint returns model year, make, model, body class, GVWR class bands, and Error Code/Error Text for a supplied 17-character VIN. The documented response does not expose the decoder/database version or a response verification timestamp required to pin the decode.
NHTSA vPIC decodes a buyer-supplied VIN and returns manufacturer-submitted make, model, model year, body class, GVWR band, and ErrorCode/ErrorText in the live response. The response concretely answers core identity/specification fields, but it does not expose the decoder/database version or a verification/retrieval timestamp required to pin the result.
VinAudit decodes the supplied VIN and returns vehicle identity attributes as part of its history response, alongside title, brand, salvage and odometer records. The cited documentation does not identify the decoder version or a dedicated decode verification timestamp; the overall report date is not documented as decoder-version provenance.
Related questions
Under Vehicle identity validityNeed Vehicle identity and specifications answered at scale?
We will test these sources on your own records, show you match and fill rates, then handle the contract, security review, and delivery into your stack.