// FOR INSURANCE AND VALUATION
The exact config, not the model.
- 1 call
- to answer the first question below.
- 2 groups
- Identity & engine and Service history.
- VIN · YMMT
- or config_key, whichever your system holds.
- free
- to prototype on the sandbox, no key.
The question this vertical asks.
A claim came in with a VIN. Which exact configuration is this, what has it had done, and what do the parts cost today?
curl 'https://vinspeclookup.com/api/v1/decode?vin=5J6RW2H82KL000007' \ -H 'Authorization: Bearer otp_live_…'{
"object": "decode",
"config": {
"config_key": "2019_honda_cr_v_ex_l15be",
"year": 2019,
"make": "Honda",
"model": "CR-V",
"trim": "EX",
"engine": "1.5L L15BE 4cyl",
"drivetrain": "4WD"
}
}The two groups that close it.
The console's structured view of each group for the reference vehicle. These are the responses a prospect asks to see first.
GET /v1/decode
2019 Honda CR-V EX
complete92% filledCanonical config resolved from a VIN, YMMT, or config_key, with the exact engine.
GET /v0/service-history
Sanitized per-VIN records, no PII, costs, or shop identity.
From response to the screen.
Which field lands where, from the response above to the screen a person actually looks at.
| Field | Where it goes |
|---|---|
| config.config_key, config.engine | The vehicle record, resolved once |
| records[].date, mileage, services | The maintenance history panel |
| services[].parts[].price.msrp | The parts basis for a repair estimate |
// IN USE
Where the response lands.
Three screens in this vertical, drawn in the site's own ASCII, each from a field in the response above.
The claim file
The exact configuration, the sanitized history and the parts basis, resolved from the VIN on the claim.
What the car has had done
Dated shop visits and owner-reported services, without PII, on a timeline.
Config, not model
Two cars with the same model name can be different configs; the decode says which one this is.
What to have ready.
Three things decide how fast an integration goes. None of them needs a key.
identifier
Which one your system already holds: a VIN, a year/make/model, or a config_key from an earlier call. A year/make/model can fit several configs; GET /v1/configs settles it once, and the config_key is stable after that.
groups
The data groups the first screen needs. Name them with include= on the vehicle call and the response carries only those, as one read. Add groups later without changing the shape.
volume
Roughly how many vehicles a day, and whether reads are interactive or batch. That picks the plan, and it tells us whether the sandbox limit will get in the way of your prototype.
// NEXT
Prototype it on the sandbox today.
The reference vehicle answers every call above with no key. When you are ready for live data across your fleet, inventory or service lane, request access and say you are building for insurance and valuation.
Other verticals: Dealer groups · Shop software · Marketplaces · Fleet and telematics