VIN → OEM Parts API

    From VIN to official OEM part number in one call

    Specialized REST API that takes a VIN and a part category and returns the current OEM part number from the manufacturer's official EPC. With SSPL supersessions applied, exploded diagram and stock availability when your ERP exposes it.

    The endpoint your DMS / ERP integration was missing

    If your team already has a working DMS, ERP or marketplace platform, you don't need another app — you need the endpoint that closes the last mile: from VIN entered to OEM part number ready to quote. That's exactly what this API does.

    Unlike a generic VIN decoder (which returns make/model/year), this API goes one step further: it crosses the decoded VIN against the manufacturer's official Electronic Parts Catalog (EPC) and returns the exact OEM part number for the category you requested, with SSPL supersessions applied automatically.

    What VIN → OEM Parts API solves

    The missing bridge between identifying a vehicle and quoting the right part.

    Official OEM part number

    Not an estimate, not an aftermarket approximation — the part number as billed by the authorized dealer.

    Live SSPL supersessions

    If the OEM replaced the part number, you get the current one automatically. Zero obsolete parts quoted.

    Standard categorization

    300+ normalized categories (brakes, suspension, filters, electrical, etc.) consistent across all OEMs.

    Exploded diagram

    When the EPC exposes it, we return the exploded diagram URL so your customer sees the part in context.

    ERP stock cross-check

    Optional endpoint that crosses the part number with your inventory and returns real availability.

    Idempotency and cache

    Repeat calls for the same VIN+category return cached response in <50 ms without spending OEM quota.

    Standard integration flow

    Designed to plug into an existing DMS or ERP without touching business logic.

    1. Your ERP sends VIN + category

    Authenticated POST call with the customer's VIN and the part category (e.g. brake_pads_front).

    2. API queries EPC + SSPL

    Decodes the VIN, identifies the corresponding OEM, queries the official EPC and applies supersessions.

    3. Returns current part number

    JSON with part number, official description, diagram and optionally cross-check with your internal stock.

    Why this endpoint is different from a generic VIN decoder

    The difference between knowing what vehicle it is and knowing what part to order from the supplier.

    • A VIN decoder returns metadata; this endpoint returns the SKU the OEM bills — ready for your purchase order.
    • Applies SSPL in real time: 18% of auto-parts part numbers change every year via supersession, and public catalogs don't reflect it.
    • Specialized endpoint by category: returns only what you asked for, not the full vehicle catalog — lighter payload, lower latency.
    • Covers motorcycles and commercial vehicles with proprietary Frame Code (Yamaha, Suzuki, Bajaj), not just 17-char ISO VIN.
    • Idempotency + L2 cache: if your ERP repeats the same query, no OEM quota is spent and the response returns in <50 ms.

    Close the last mile of your integration with a single endpoint

    We give you sandbox with 1,000 calls and a sample VIN+category pair decoded against the official EPC.

    DEVELOPER EXPERIENCE

    VIN + category → current OEM part number

    Dedicated endpoint. Minimal response. Built for your ERP, not your marketing team.

    Request
    curl -X POST https://api.eitserv.tech/v1/vin/parts \
      -H "Authorization: Bearer $EITS_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{
        "vin": "JTDKARFU8K3079482",
        "category": "brake_pads_front",
        "apply_sspl": true,
        "include_diagram": true
      }'
    Response200 OK · 127ms
    {
      "vin": "JTDKARFU8K3079482",
      "category": "brake_pads_front",
      "part": {
        "oem_part_number": "04465-47080",
        "description": "Pad Kit, Disc Brake Front",
        "supersedes": ["04465-47070", "04465-47060"],
        "current": true,
        "diagram_url": "https://cdn.eitserv.tech/epc/toyota/jtd-prius-2019-fbrake.svg"
      },
      "source": "toyota_tis_official",
      "cached": false,
      "latency_ms": 284
    }

    VIN → OEM Parts vs the rest of the market

    Why a specialized endpoint beats a generic decoder for ERP integrations.

    FeatureEITS /vin/partsGeneric decoderEPC scraping
    Returns OEM part numberYesNoPartial
    Live SSPL supersessionsYes (auto)NoManual
    Exploded diagramYesNoVariable
    Idempotency + L2 cacheYes (<50 ms)NoNo
    Complies with OEM T&CYes (agreement)N/ANo
    Motorcycles / Frame CodeYesNoRare

    How it plugs into your DMS / ERP

    Lightweight middleware. No changes to your business logic.

    01

    Client DMS / ERP

    Event: customer requests part quote.

    02

    EITS middleware

    Calls POST /v1/vin/parts with VIN + category.

    03

    Decode + EPC

    Validates VIN, identifies OEM, queries official catalog.

    04

    SSPL + cache

    Applies supersessions, stores in idempotent L2 cache.

    05

    ERP receives SKU

    Your ERP generates the quote with the current part number.

    Frequently Asked Questions

    Everything you need to know before getting started.