VIN Decoder API

    VIN Decoder API — chassis to OEM part number in <150 ms

    A REST VIN decoder API that decodes 17-character VINs against official OEM catalogs (not scraped), validates the check digit with the ISO 3779 formula and returns make, model, year, assembly plant and SSPL supersessions — ready for your ERP, CRM or AI agent.

    Why a serious VIN decoder API matters for auto parts

    Free VIN APIs like NHTSA vPIC are fine to identify a vehicle sold in the US, but they don't return the OEM part number, don't validate SSPL supersessions and poorly cover Latin American assembly plants. Selling parts without returns requires more: a VIN decoder API wired into the manufacturer's official Electronic Parts Catalog.

    Our VIN decoder API is the same technical layer that powers AutoParts AI Agent inside dealerships across Mexico, Colombia, Argentina, Chile, Peru and the Dominican Republic. We expose it as an authenticated REST endpoint so your team can integrate it directly in your ERP, internal app or your own AI agent.

    P50 latency under 150 ms, P95 under 400 ms. Enterprise 99.9% SLA. OpenAPI 3.1 documentation, TypeScript and Python SDKs and dedicated technical support.

    What this VIN decoder API actually does

    More than a generic decoder — an API built for selling auto parts.

    ISO 3779 check-digit validation

    Applies the position-9 verification formula and rejects malformed VINs before spending a catalog call.

    Full 17-character decoding

    WMI (1–3), VDS (4–9) and VIS (10–17). Returns make, model, body, engine, model year and assembly plant.

    Official EPC connection

    Authenticated calls to Toyota TIS, Nissan FAST, Honda iN, Suzuki, JLR Topix and more. Returns OEM part numbers, not guesses.

    Live SSPL supersessions

    Cross-checks the requested part against the OEM's live SSPL table and returns the current part number, not the legacy one.

    Normalized JSON response

    Consistent schema across OEMs. Your ERP integrates once and supports new brands without touching code.

    Enterprise rate limits

    10,000 req/min by default, scalable under SLA. No surprises during end-of-month demand spikes.

    How to use the VIN decoder API

    Three HTTP calls and your system quotes parts like a factory-authorized dealer.

    1. POST /v1/vin/validate

    Send the VIN. The API validates format, check digit and rejects invalid VINs before spending OEM catalog quota.

    2. POST /v1/vin/decode

    Returns the structured JSON: WMI, VDS, VIS, make, model, year, engine, plant, country of assembly and destination market.

    3. POST /v1/vin/parts

    With the decoded VIN and a part category, returns OEM part numbers, live SSPL supersessions and the exploded diagram when available.

    What sets this VIN decoder API apart from free ones

    The technical detail that separates identifying a vehicle from quoting the right part.

    • NHTSA vPIC covers vehicles sold in the US — systematically fails on LatAm VINs with local assembly plants (Mexico, Brazil, Argentina).
    • Scraped APIs (Carfax-likes) expose vehicle metadata but never the OEM part number or live SSPL supersessions.
    • This API connects directly to the manufacturer's EPC using authorized dealer credentials — no estimates.
    • Returns the assembly plant (position 11), critical because two units of the same model can carry different part numbers depending on plant.
    • Supports motorcycles and commercial vehicles with proprietary Frame Code (Yamaha, Suzuki, Bajaj) in addition to the 17-char ISO VIN.

    Try the VIN decoder API with your first real VIN

    We give you sandbox access and a sample VIN decoded against the official EPC. No card, no commitment.

    DEVELOPER EXPERIENCE

    One HTTP call. Response ready for your ERP.

    No proprietary SDK, no lock-in. Plain REST, normalized JSON across OEMs.

    Request
    curl -X POST https://api.eitserv.tech/v1/vin/decode \
      -H "Authorization: Bearer $EITS_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{
        "vin": "JTDKARFU8K3079482",
        "include": ["plant", "engine", "supersessions"]
      }'
    Response200 OK · 127ms
    {
      "vin": "JTDKARFU8K3079482",
      "valid": true,
      "check_digit_ok": true,
      "wmi": "JTD",
      "make": "Toyota",
      "model": "Prius",
      "model_year": 2019,
      "body": "Hatchback 5D",
      "engine": "1.8L 2ZR-FXE Hybrid",
      "plant": { "code": "K", "name": "Tsutsumi, Japan" },
      "market": "LatAm",
      "source": "toyota_tis_official",
      "latency_ms": 127
    }

    VIN Decoder API vs market alternatives

    Technical comparison against the APIs ranking on the "vin decoder api" SERP.

    FeatureEITS APINHTSA vPICDataOneCarAPI
    Official OEM EPC connectionYes (8 OEMs)NoPartialNo
    Returns OEM part numberYesNoYesNo
    Live SSPL supersessionsYesNoNoNo
    LatAm coverage (local plants)YesLimitedLimitedNo
    P50 latency<150 ms~800 ms~500 ms~400 ms
    Motorcycles / Frame CodeYesNoNoNo
    Enterprise 99.9% SLAYesBest effortYesYes

    Architecture: from customer frontend to OEM part number

    Sovereign infrastructure, optional self-hosted, no public-cloud lock-in.

    01

    Your Frontend / ERP

    User enters the VIN on your store, app or internal system.

    02

    EITS API Gateway

    JWT auth + rate limit + ISO 3779 check-digit validation.

    03

    OEM EPC catalog

    Authenticated call to official EPC (Toyota TIS, Nissan FAST, etc).

    04

    SSPL engine

    Applies live supersessions and normalizes JSON across brands.

    05

    Response to your ERP

    Current part number ready to quote — total <500 ms P95.

    Frequently Asked Questions

    Everything you need to know before getting started.