Vehicle · head-to-head

Kelley Blue Book vs NHTSA

Kelley Blue Book

Kelley Blue Book's Cox Automotive-run API program (IDWS, Advertising Data, Instant Cash Offer, and Batch VIN) provides vehicle valuation, pricing, and configuration data behind an approval-gated API key, per developer.kbb.com's own access instructions. Its legacy Swagger doc-viewer content pages (/content/data/*.html) now 404 into the site's SPA shell — orphaned — but the surrounding portal, the key-request process, and Cox Automotive's successor developer platforms (developer.coxautoinc.com, coxautoinc.mashery.com) all remain live over HTTPS, confirming https true and that the program has moved rather than gone dead; cors could not be re-probed live since no public endpoint or key is available. Access requires Cox Automotive approval with no public self-serve signup — paid.

NHTSA

NHTSA's vPIC (vehicle Product Information Catalog) API decodes VINs and looks up makes, models, and manufacturer/WMI data straight from the US government's own vehicle registry, with no signup required. A fresh live fetch of the vPIC operation index in this run lists 24 `/api/vehicles/*` operations and confirms none of them is a recall lookup — that's a separate NHTSA product (nhtsa.gov/recalls), not part of this API, correcting a prior run's summary. A live GET and OPTIONS preflight against vpic.nhtsa.dot.gov/api/vehicles/getallmakes both returned access-control-allow-origin: *, reconfirming cors "yes"; auth "None" and https were reconfirmed on the same calls. Responses are available in both JSON and XML via a format query parameter (XML is the live-confirmed default) — free, unlimited US government open data.

Kelley Blue BookNHTSA
AuthenticationAPI KeyNone
Pricingpaidfree
FormatsJSONJSON, XML
CORSnoyes
HTTPSYesYes

NHTSA needs no API key, while Kelley Blue Book requires API Key — pick NHTSA to start without signup.

More comparisons