Vehicle specifications API
Factory specifications keyed by VIN: engine, drivetrain, dimensions, fuel economy and equipment for the exact trim a vehicle was built as.
Because the lookup is by VIN rather than by model name, the response describes one car rather than an average of a model year.
Endpoints this uses
| Endpoint | Path | What it contributes |
|---|---|---|
| Vehicle Specifications | GET /v1/vehicles/specifications/{vin} | Factory specifications for a specific VIN. |
| VIN Decode | GET /v1/vehicles/vin/{vin} | Resolve a VIN to the trim whose specs you want. |
| Ownership Costs | GET /v1/vehicles/ownership-costs | Ownership cost projections built on those specifications. |
Why VIN-keyed instead of model-keyed
A model name is ambiguous: two cars sharing a name and year can differ in engine, drivetrain and equipment. A VIN is not ambiguous, so specifications resolve to one build rather than a range.
That precision matters most downstream — ownership-cost and valuation models built on an averaged trim inherit the averaging error.
Pricing
The free Starter plan includes 1,000 calls a month shared across all eleven synchronous vehicle data APIs, plus $10 of one-time credit for usage after that allowance.
Credits never expire and are spent per successful call.
Frequently asked questions
- Are specifications trim-specific?
- Specifications are keyed by VIN, so the response describes the exact trim that VIN was built as rather than a generic model-year average.
- What if I only have a make and model?
- Decode the VIN first. The decode response names the trim, and the specifications endpoint takes the same VIN.
Related
- Car API
VIN decode, specifications, recalls and market pricing in one REST API.
- Automotive data API
Valuation, depreciation, ownership costs and marketplace listings.
- Car makes and models API
Make, model, year and trim resolved from a VIN.
- Car prices by model
Median asking prices and model-year curves from 1.5M listings.
- All endpoints
Every documented endpoint with pricing and examples.