Decode Failures

Understanding how NeoVIN handles VIN decode failures, including reasons and structured responses.

Handling VIN Decode Failures

NeoVIN is designed to decode VINs accurately and efficiently, but there are scenarios where a VIN may not be decodable. This can happen for various reasons, such as the VIN being invalid, not found in the database, or lacking sufficient data for a complete decode.

In such cases, NeoVIN provides a clear and structured response to inform users about the failure and the reason behind it. The response will include an observation field that explains why the VIN could not be decoded. This field is crucial for understanding the limitations of the decode process and helps users identify potential issues with the VIN or the data available for that VIN.

Decode Error Reasons

When VIN decoding fails, the response includes specific reason codes explaining the failure:

Reason CodeExplanation
UNDETERMINED TRIM|VALID VIN|TRUCKTrim information unavailable; VIN classified as truck
UNDETERMINED TRIM|VALID VIN|PASSENGER CARTrim information unavailable; VIN classified as passenger car
UNDETERMINED TRIM|VALID VIN|MPVTrim information unavailable; VIN classified as MPV
UNDETERMINED TRIM|VALID VIN|INCOMPLETE VEHICLETrim information unavailable; VIN classified as incomplete vehicle
UNDETERMINED TRIM|VALID VIN|BUSTrim information unavailable; VIN classified as bus
UNDETERMINED TRIM|INVALID VINTrim information unavailable; VIN deemed invalid
UNDETERMINED TRIMTrim information unavailable based on available data
NO SPECS|VALID VIN|TRUCKValid VIN; specifications unavailable; classified as truck
NO SPECS|VALID VIN|TRAILERValid VIN; specifications unavailable; classified as trailer
NO SPECS|VALID VIN|PRIOR TO 1997Valid VIN; predates 1997; system does not support pre-1997 vehicles
NO SPECS|VALID VIN|PASSENGER CARValid VIN; specifications unavailable; classified as passenger car
NO SPECS|VALID VIN|MPVValid VIN; specifications unavailable; classified as MPV
NO SPECS|VALID VIN|MOTORCYCLEValid VIN; specifications unavailable; classified as motorcycle
NO SPECS|VALID VIN|LOW SPEED VEHICLE (LSV)Valid VIN; specifications unavailable; classified as LSV
NO SPECS|VALID VIN|INCOMPLETE VEHICLEValid VIN; specifications unavailable; classified as incomplete vehicle
NO SPECS|VALID VIN|COMPLETE VEHICLEValid VIN; specifications unavailable from provider
NO SPECS|VALID VIN|BUSValid VIN; specifications unavailable; classified as bus
NO SPECS|INVALID VINSpecifications unavailable; VIN deemed invalid
NO SPECSSpecifications unavailable from provider
NO HISTORY FOUNDVehicle not encountered in MarketCheck listings
NO HISTORY FOUND|SINGLE SPEC DATAVehicle not in listings; single specification available

If NeoVIN cannot decode the VIN:

  • It may return generic specification data (if available).
  • The response will include an observation field with a clear reason.
  • The API returns an HTTP 422 status when the VIN is invalid or the decoder cannot determine any match.
  • The observation field is only included when the VIN cannot be decoded.
  • Exception: If the reason is NO HISTORY FOUND|SINGLE SPEC DATA, then the response will include both basic decoded data and the observation.