Specs, values, and recalls

AutoHub Vehicle API

Decode a VIN, or walk from a model year to its makes, models, and trims. Then read the vehicle's details, its trade-in and private-party value, its depreciation, its recalls, and the dealers near a US ZIP code.

Capabilities

What you can do with the AutoHub API

There are two starting points. A VIN identifies one exact vehicle, while a year, make, and model identify a model. The make, model, and trim lists come from EPA fueleconomy.gov data.

Make, model, and trim

Pass a model year to list its makes, a make to list its models, and a model to list its trims. The ids are the EPA names, such as CX-5 4WD, and each trim carries the EPA vehicle_id that the recalls endpoint accepts. See examples

Model details

Details takes a year, make, and model and returns the category, available years, other models from the same make, specs, and trims. It also adds NHTSA crash-test ratings for up to three variants, or null when NHTSA has none. See examples

VIN decode

A 17-character VIN returns the trim, body style, engine, transmission, and drivetrain of that exact vehicle, with the year, make, and model from NHTSA vPIC. It also returns the vehicle_id that the value and depreciation endpoints need. See examples

Recalls

Recalls returns NHTSA recall campaigns with the summary, affected component, consequence, remedy, report date, and campaign number. You can identify the vehicle by year, make, and model, by VIN, or by vehicle_id. See examples

Value and depreciation

Car value returns a trade-in value, or private-party values by condition, at the mileage and ZIP code you send, each with a low and high range. Depreciation returns trade-in and private-party values year by year, with each year flagged as past or projected. See examples

Dealers

Pass a US ZIP code and a make to get that make's dealers nearby. Each dealer comes with its name, address, phone, website, and distance in miles. See examples

Shortened examples

Sample responses

Each sample is a trimmed body from one endpoint, cut down so the field names are easy to read. A live call also includes a meta object, and the values shown are examples.

{
  "vin": "JM3KKBHA5R1166850",
  "body": {
    "trim_name": "Preferred Sport Utility 4D",
    "body_style": "SUV",
    "engine": "4-Cyl, e-SKYACTIV, Hybrid, 2.5 Liter",
    "transmission": "Automatic, 8-Spd e-SKYACTIV-Drive",
    "drivetrain": "AWD"
  }
}
{
  "displayName": "2.5 S Sport Utility 4D",
  "combinedMpg": "26 MPG",
  "horsepower": "187 @ 6000 RPM",
  "engine": "4-Cyl, SKYACTIV-G, 2.5 Liter",
  "driveTrain": "AWD",
  "towingCapacity": 2000,
  "zeroToSixty": 8.9
}
{
  "make": "Mazda",
  "model": "CX-5",
  "year": 2024,
  "specs": {
    "horsepower": "187 @ 6000 RPM",
    "torque": 186,
    "mpg_city": 24,
    "mpg_hwy": 30,
    "fuel_tank": "15.3 Gal"
  },
  "features": [
    "Blind Spot Monitoring",
    "AWD",
    "Apple CarPlay"
  ]
}
{
  "make": "mazda",
  "model": "cx-5",
  "year": 2023,
  "body": {
    "totalThreeYearDepreciation": 9225,
    "currentResaleValue": 18850,
    "currentTradeInValue": 17050,
    "historicalValues": [
      {
        "year": 2023,
        "resaleValue": 28075
      }
    ]
  }
}
{
  "id": 7771155,
  "name": "The Autobarn Mazda of Evanston",
  "distance": 11,
  "location": {
    "address": "1015 Chicago Avenue",
    "city": "Evanston",
    "state": "IL",
    "zip": "60202"
  },
  "phone": "224-307-8496",
  "website": "https://www.mazdaofchicagoland.com"
}

Documentation

The AutoHub docs cover the make, model, and trim lookups, VIN decoding, model details, car value, depreciation, recalls, and dealers. They also explain which vehicle_id each endpoint expects: the EPA id from the trims list or the one from VIN decode.

Code samples

Every endpoint in the documentation includes a sample request in Shell, JavaScript, PHP, and Python.

ShellShellJavaScriptJavaScriptPHPPHPPythonPython

View documentation

Pricing

One plan covers every API

Your plan's monthly requests work on this API and every other SteadyAPI API. Plan details, overage rates, and the Free plan's daily cap are on the pricing page. Need more volume than the largest plan? Email [email protected].

Free
$0.00
$9.99
per month
Starter
$14.99
$19.99
per month
Developer
$39.99
$59.99
per month
Business Popular
$89.99
$99.99
per month
Enterprise
$299.99
$499.99
per month
SubscribeSubscribeSubscribeSubscribeSubscribe
Requests per month50010,00050,0002,500,000
Stock Market API
Options Data API
Crypto Data API
AliExpress API
Reddit API
Booking.com API
Real Estate API
Baseball (MLB) API
Hockey API
Football API
Amazon API
eBay API
Walmart API
Instagram API
Twitter / X API
TikTok API
YouTube API
AutoHub API
ScrapeFlow
Commercial Use
Optional overage rate*$1.50 per 1,000 requests$1.05 per 1,000 requests$0.09 per 1,000 requests
Overage capup to 50,000 extraup to 250,000 extraup to 12,500,000 extra
Free
$0.00
$94.99
per year
Starter
$11.96
$14.35
per month$143.52 billed yearly
Developer
$32.50
$40.00
per month$389.99 billed yearly
Business Popular
$72.50
$90.00
per month$869.99 billed yearly
Enterprise
$320.83
$400.00
per month$3,849.99 billed yearly
SubscribeSubscribeSubscribeSubscribeSubscribe
Requests per month50010,00050,0002,500,000
Stock Market API
Options Data API
Crypto Data API
AliExpress API
Reddit API
Booking.com API
Real Estate API
Baseball (MLB) API
Hockey API
Football API
Amazon API
eBay API
Walmart API
Instagram API
Twitter / X API
TikTok API
YouTube API
AutoHub API
ScrapeFlow
Commercial Use
Optional overage rate*$1.50 per 1,000 requests$1.05 per 1,000 requests$0.09 per 1,000 requests
Overage capup to 50,000 extraup to 250,000 extraup to 12,500,000 extra

* Overage is optional and stays off until you turn it on in Billing. It is available on paid plans billed by card through Stripe, and not during a trial. Usage is counted in monthly periods that start on your billing day, yearly plans included. Requests past the included limit are charged at the plan's rate for each started block of 1,000, up to the overage cap, on one invoice after the period ends. Amounts under $0.50 carry over to the next invoice. If you change plans during a period, the limit and overage rate of the plan you are on when the period ends apply to the whole period.

The Free plan is also capped at 20 requests per day (New York time). Requests count by endpoint weight, and only responses with HTTP status 200 count.

Commercial use is included only on the plans that list it. If you are not sure whether your project counts as commercial use, email [email protected] before you launch.

Why SteadyAPI

Ids that carry between calls

Two kinds of vehicle_id move between endpoints. Knowing which one each call expects saves you a failed request.

EPA names as ids

The make and model lists return EPA names as makeId and modelId. Pass them back unchanged; numeric make ids are rejected.

Value needs the VIN id

Car value and depreciation take the vehicle_id returned by VIN decode, not the EPA id from the trims list.

Recalls from any starting point

Recalls accepts year, make, and model, a VIN, or either kind of vehicle_id. When you send more than one, year, make, and model take precedence, then the VIN, then the id.

Value at a mileage and ZIP

Value and depreciation take the current mileage and an optional ZIP code for regional pricing. Depreciation also accepts a condition and an annual mileage for its projection.

Also on the blog

From the blog

These posts come from across SteadyAPI, so the one at the top may be about a different API. The reference for this page is the documentation above.

How to Search Hotels Using SteadyAPISep 25, 2026

How to Search Hotels Using SteadyAPI

Learn how to find hotels by destination using SteadyAPI. Resolve a place name to coordinates, then pull property names, ratings, and prices with the Booking.com hotel search endpoints.

READ MORE
Predicting Property Value Trends: How to Use Real Estate Valuation APIsJul 19, 2026

Predicting Property Value Trends: How to Use Real Estate Valuation APIs

Learn how to build a predictive real estate valuation pipeline using SteadyAPI. This guide shows developers how to combine historical property values, multi-provider forecasts, neighborhood market trends, housing market indicators, and comparable sales data to power automated valuation models (AVMs), investment analytics, and property intelligence platforms with structured real-time API data.

READ MORE
How to Fetch Local School Ratings and Neighborhood Amenities via APIJul 19, 2026

How to Fetch Local School Ratings and Neighborhood Amenities via API

Neighborhood insights are just as important as the property itself. This guide shows developers how to use the SteadyAPI Neighborhood Amenities API to fetch school ratings, walkability and transit scores, and nearby amenities through a single endpoint. You'll learn how to authenticate requests, retrieve structured neighborhood data, filter schools and local businesses, and combine these metrics into a custom neighborhood quality score. Whether you're building a real estate marketplace, property valuation model, or location intelligence dashboard, this tutorial helps you enrich listings with valuable contextual data while reducing the complexity of managing multiple third-party integrations.

READ MORE
The Developer’s Guide to Integrating Real-Time MLS Property DataJul 19, 2026

The Developer’s Guide to Integrating Real-Time MLS Property Data

This guide walks developers through building a modern real estate data pipeline with SteadyAPI. You'll learn how to search MLS property listings, retrieve tax and transaction histories, analyze local housing market trends, and enrich property data with neighborhood and environmental insights. Instead of maintaining fragile web scrapers or navigating complex MLS integrations, SteadyAPI provides structured JSON APIs that simplify property data ingestion and help you build faster, more reliable real estate applications. Whether you're creating an investment platform, property valuation engine, market research tool, or analytics dashboard, this tutorial covers the essential endpoints and architecture needed to get started.

READ MORE