// FOR FLEET AND TELEMATICS
Maintenance due, per vehicle.
- 1 call
- to answer the first question below.
- 2 groups
- Maintenance schedule and Fluids & capacities.
- VIN · YMMT
- or config_key, whichever your system holds.
- free
- to prototype on the sandbox, no key.
The question this vertical asks.
We have odometer readings for every vehicle. Which ones are due, for what, and how much oil does each take?
curl 'https://vinspeclookup.com/api/v1/maintenance-schedule?vin=5J6RW2H82KL000007' \ -H 'Authorization: Bearer otp_live_…'{
"object": "maintenance_schedule",
"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"
},
"intervals": [
{
"confidence": 0.85,
"display": null,
"interval_miles": 7500,
"interval_months": 12,
"mechanic_verified": false,
"name": "Oil Change",
"service": "oil_change"
},
{
"confidence": 0.9199999999999999,
"display": null,
"interval_miles": 7500,
"interval_months": 6,
"mechanic_verified": false,
"name": "Tire Rotation",
"service": "tire_rotation"
}
],
"meta": {
"generated_at": 1792323140145
}
}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/maintenance-schedule
2019 Honda CR-V EX
complete92% filledService intervals by miles and months.
GET /v1/fluids
2019 Honda CR-V EX
complete92% filledFluid types and capacities for the exact engine, each with its source, not a generic 'takes 5 quarts'.
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 |
|---|---|
| intervals[].interval_miles | Compared with the odometer feed to flag due vehicles |
| intervals[].service | The work-order type for the service scheduler |
| specs[] oil_capacity_qts | Bulk fluid planning across the fleet |
// 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 fleet board
Every vehicle's odometer against its own service interval; the due ones flag themselves.
Miles and months, per vehicle
The schedule for each config, not a fleet-wide guess, so a van and a pickup are not on the same clock.
Bulk fluids
Capacity per vehicle times the count, for the drum order.
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 fleet and telematics.
Other verticals: Dealer groups · Shop software · Marketplaces · Insurance and valuation