Data API / VIN electrification

A clean API for battery lifecycle records.

Decode VINs, classify electrification, and return battery fields that can feed pricing, intake, condition-report, inventory, and purchasing software.

Get API access Read reference

Python

import requests

url = "https://api.autoresourceco.com/api/v1/vin/decode"
headers = {
    "X-API-Key": "your_api_key_here",
}
params = {
    "vin": "5YJ3E1EA1JF123456",
}

response = requests.get(url, headers=headers, params=params, timeout=15)
print(response.json())

example response full reference

{
  "VIN": "1n4az1bv3nc561510",
  "Year": 2022,
  "Make": "NISSAN",
  "Model": "Leaf",
  "Trim": "S",
  "ElectrificationLevel": "BEV",
  "technical_details": {
    "body_class": "Hatchback/Liftback/Notchback",
    "vehicle_type": "PASSENGER CAR",
    "drive_type": "4x2",
    "fuel_type_primary": "Electric",
    "fuel_type_secondary": null,
    "series": null,
    "ev_drive_unit": null,
    "battery_type": null,
    "battery_energy_kwh_from": null,
    "battery_energy_kwh_to": null,
    "battery_voltage_from": null,
    "battery_voltage_to": null,
    "battery_modules_per_pack": null,
    "battery_cells_per_module": null,
    "charger_level": null,
    "charger_power_kw": "40",
    "wheel_base_inches": null,
    "curb_weight_lbs": null,
    "gvwr": "Class 1: 6,000 lb or less (2,722 kg or less)",
    "track_width_inches": null,
    "engine_configuration": null,
    "engine_cylinders": null,
    "displacement_l": null,
    "transmission_style": "Continuously Variable Transmission (CVT)",
    "air_bag_locations": null,
    "manufacturer_id": null,
    "plant_city": "SMYRNA",
    "plant_country": "UNITED STATES (USA)",
    "plant_company_name": "Nissan North America Inc."
  }
}

Response schema

Fields meant for downstream operator systems.

vin	normalized vehicle identification number
electrification	HEV, PHEV, BEV, FCEV, or ICE classification
battery	pack family, chemistry, and fitment fields when available
value	battery value and purchasing context for operator review
confidence	match quality metadata for downstream decisions

Auction condition reports

Wholesale valuation feeds

VIN batch decode queues

EAMS and inventory systems

What the API returns

Get the data you need in the place you need it.

The response is easy to inspect: fields, confidence, and the places a product team can use the data.

API response preview

Example structure for an endpoint explorer, product integration view, or response diff.

response preview JSON

{
  "electrification": "BEV",
  "battery_family": "platform-specific pack",
  "chemistry": "returned when determinable",
  "confidence": "review | high | needs evidence",
  "workflow_flags": ["buyer display", "valuation input"]
}

request

VIN or lot record

Works as lookup, batch, or product feature input.

response

electrification + battery context

Structured fields for downstream systems.

confidence

match quality and review flags

Keeps ambiguous records from looking certain.

Enterprise fit

Designed for data teams that already own the vehicle workflow.

ARC does not need to replace a marketplace, VIN decoder, appraisal tool, or inspection system. It adds the EV and hybrid battery layer those systems usually miss.

Auction workflow

Condition report enrichment

Return battery context beside photos, OBD notes, inspector observations, and seller disclosures.

pack / chemistry / capacity / hazard

Valuation model inputs

Normalize EV, PHEV, HEV, and FCEV records before they enter pricing, guarantee, or residual-value workflows.

electrification / fitment / confidence

Dealer buyer confidence

Expose buyer-facing EV details that help non-specialist dealers understand what they are bidding on.

badges / replacement context / next checks

integration workflow

source record

ARC enrichment

battery_family matched

workflow_flag review

workflow action

Endpoint output appears beside the product or data workflow that uses it.

API outcome

ARC data becomes a product feature or workflow rule inside your existing system.

Where the API changes the product

The response becomes a product action, not just a database field.

API buyers care about the exact feature or operation the data makes possible: badge, prompt, valuation input, routing flag, or report field.

Vehicle record enters

input

A VIN, listing, appraisal, or inventory record reaches the product workflow your team already owns.

ARC returns battery context

api

The API response adds electrification, likely pack fields, chemistry context, and confidence metadata.

Product decides what to show

product

Your system can display a badge, trigger a prompt, route a record, or feed a valuation model.

Data team monitors quality

quality

Confidence and review flags keep edge cases visible instead of hiding uncertainty in a plain field.

The next action is clearer: route, price, disclose, or integrate.

Endpoint matrix

Start with VIN decode, then expand by use case.

Open docs

method	endpoint	returns	reference
GET	/api/v1/vin/decode	Resolve a 17-character VIN to a normalized vehicle record with electrification fields and technical details.	open
POST	/api/v1/vin/decode-batch	Decode multiple VINs in one request and receive successful results plus per-VIN validation or upstream failures.	open
GET	/api/v1/explorer/vehicle/by-vin	Decode a VIN and return the vehicle payload plus minimal battery attributes for chemistry and compliance workflows.	open
GET	/api/v1/explorer/vehicle/by-ymm	Retrieve Explorer battery candidates when VINs are unavailable and you only know year, make, and model.	open

Explorer and API share a data model.

Teams can inspect a record visually, then use the same fields inside an intake or pricing system.

Usage follows Professional or Enterprise access.

API usage is available on paid plans. Review the pricing page for plan limits and billing behavior.

No special client required.

Use standard authenticated HTTPS requests from existing systems and automation tools.

View pricing Use visual Explorer