VehiCode
PlatformAPIResourcesPricing

VIN Decoder API

VIN Decoder API for vehicle identification

VehiCode helps developers decode VINs into structured vehicle data for automotive platforms, internal tools, marketplaces, and subscriber API integrations.

POST /api/decodeJSON vehicle report

VIN segments, vehicle identity fields, optional specs, and monthly usage metadata.

Free returns basic fields; paid plans unlock premium specs where available.

Vehicle Identification API

What is the VehiCode VIN Decoder API?

The VehiCode VIN Decoder API is a developer-facing endpoint for turning a VIN into a compact public vehicle report. It normalizes vehicle identification data, returns usage metadata, and includes available technical specifications.

01

Developer-first JSON

Responses are designed for backend integrations: predictable JSON, stable field names, and usage metadata with each subscriber request.

02

Clear technical certainty

Confirmed specifications, estimates, and possible configurations remain distinct, so applications can present vehicle data appropriately.

03

Correction workflow

Subscriber systems can report incorrect decodes for review, which creates a practical feedback loop for improving vehicle data quality over time.

European VIN decoding

Built for European VIN decoding workflows

European vehicle data is messy in a very practical way. The same model can appear under different names across markets, body styles are not always encoded consistently, and public VIN sources often stop before they become useful for real product workflows.

VehiCode returns available vehicle data in a consistent format and accepts correction reports when a vehicle has been identified incorrectly.

Market namingBody-style normalizationReviewed corrections

Vehicle data API

What data can be decoded?

Responses include available VIN structure and vehicle identity. Free access provides basic information. Starter and Business may include engine, fuel, power, transmission, dimensions, weights, and other technical data where available.

VIN structure

  • vin
  • wmi
  • vds
  • vis
  • checkDigit
  • yearCode
  • plantCode
  • serialNumber
  • validFormat

Vehicle identity

  • manufacturer
  • model
  • modelCode
  • generation
  • bodyStyle
  • possibleBodyStyles
  • trim
  • vehicleType
  • region
  • modelYear

Basic specs

  • engine
  • fuelType
  • transmission

Premium specs

  • driveType
  • powerKw
  • powerHp
  • displacementCc
  • batteryCapacityKwh
  • emissionsStandard
  • market

Optional technical specs

  • lengthMm
  • widthMm
  • heightMm
  • wheelbaseMm
  • curbWeightKg
  • grossWeightKg
  • groundClearanceMm
  • cargoVolumeLiters
  • cargoVolumeMaxLiters

Attribution

Data Sources

Where applicable, VehiCode uses vehicle type-approval data from the Swiss Federal Roads Office (ASTRA/FEDRO) TAS open dataset. Responses using this data include an X-Data-Attribution header.

Decode VIN API

Example API request and response

Use x-api-key for subscriber usage. Authorization: Bearer is also supported.

Open reference
RequestPOST
curl -X POST https://vehicode.eu/api/decode \
  -H "Content-Type: application/json" \
  -H "x-api-key: vdx_your_api_key" \
  -d '{"vin":"WVWZZZAUZHP507470"}'
Response200 OK
{
  "report": {
    "vin": "WVWZZZAUZHP507470",
    "wmi": "WVW",
    "vds": "ZZZAUZ",
    "validFormat": true,
    "manufacturer": "Volkswagen",
    "model": "Golf",
    "bodyStyle": "Combi",
    "modelYear": "2017",
    "region": "Europe"
  },
  "metadata": {
    "plan": "business",
    "upgradeAvailable": false,
    "premiumFieldsAvailable": 0
  },
  "usage": {
    "limit": 2500,
    "remaining": 2499,
    "resetAt": "2026-08-01T00:00:00.000Z"
  }
}

VIN Lookup API

Supported use cases

01

Vehicle marketplaces

Pre-fill listing fields and normalize vehicle labels from VIN input.

02

Dealer inventory

Decode VINs during acquisition, appraisal, import, and stock intake.

03

Fleet and leasing

Keep vehicle records consistent across countries, vendors, and internal tools.

04

Inspection workflows

Attach cleaner vehicle identity data to intake, handover, and correction processes.

Pricing

Start free, scale when needed

Free0 EUR25 requests / month
Business29 EUR / monthTax calculated at checkout2,500 requests / month. Everything in Starter with priority support.
EnterpriseCustomCustom limits, SLA, integrations, and dedicated infrastructure options.

These are monthly base prices before applicable tax. Stripe Checkout shows the final tax-inclusive total after you enter your billing details and before you pay.

Compare pricing

FAQ

QuestionWhat is a VIN Decoder API?

A VIN Decoder API accepts a vehicle identification number and returns structured vehicle data that software can store, validate, or use to pre-fill workflows.

QuestionHow should I interpret technical specifications?

Confirmed specifications, estimates, and possible configurations are kept separate where available. Possible configurations do not identify the exact vehicle build.

QuestionIs VehiCode focused on European VIN decoding?

Yes. VehiCode supports European vehicle data workflows, including regional naming and body-style differences. Available detail varies by VIN.

QuestionHow do API limits work?

The Free plan includes 25 requests / month. Starter includes 500 requests / month. Business includes 2,500 requests / month. Limit and reset metadata is returned with API responses.

QuestionCan incorrect decodes be reported?

Yes. Subscriber integrations can send correction reports with the expected manufacturer, model, body style, model year, and a note for admin review.

Related

Start building

Integrate VIN decoding into your product

Create an account, generate an API key, and test the decode endpoint from your backend workflow.

Get API key