Classic.com Data Parser & API
Classic.com is the leading collector-car search engine — used by 2M+ enthusiasts — aggregating listings and results from auctions, dealers and private sellers across the market, and Carapis can extract its full aggregated data, including cross-platform sold-price history, through one REST API. Rather than one marketplace, Classic.com is a meta-source that unifies the fragmented collector market into one comparable dataset.
On request — not in the live feed today. We do not continuously crawl Classic.com right now. Activation takes 2–3 weeks of engineering and is quoted per source, because each one ships with dedicated proxies, anti-bot tuning and ongoing maintenance. Ask us to add it.
| Country | USA |
|---|---|
| Type | Aggregator |
| Vehicle types | classic |
| Monthly visits | mid-tier; 2M+ users |
| Active listings | aggregates auctions/dealers/private |
| API access | No public API (parse-only) |
| Parse priority | ★★★☆☆ |
| Official site | www.classic.com |
What is Classic.com?
Classic.com is a US-based search engine and aggregator for the collector, exotic and specialty car market, with 2M+ users. It indexes live and sold listings from many auction houses, dealers and private sellers, and pairs them with model-level price history and market-trend analytics. Because it consolidates the whole collector market rather than a single venue, Classic.com is uniquely positioned as a cross-platform price-history source.
Market Position
Classic.com is the reference search engine for collector-car data, drawing 2M+ users and aggregating across auctions, dealers and private sales (Classic.com market report, Sep 2025). Online collector auctions now move 50K+ cars/yr (~$2.5B), surpassing live auctions — and Classic.com sits above that fragmented landscape, normalizing listings and results from dozens of venues into one model-indexed dataset. That makes a single Classic.com parser effectively a cross-market price-history feed for collector vehicles.
What the API returns
Response schema
Indicative — this is the shape, not a guarantee. Every source returns the same structure, so what you build against does not change when you add one. Which fields carry a value depends on the source and on the individual listing: a site that does not publish mileage returns null there, and Classic.com is no exception.
List — GET /apix/api/vehicles/ — returns 30 fields per vehicle:
idstringsource_codestringbrand_namestringbrand_slugstringmodel_namestringmodel_slugstringtrimstringyearintegerprice_usdintegermileageintegerfuel_typeFuelTypeEnumtransmissionTransmissionEnumbody_typeBodyTypeEnumcolorColorEnumseller_typeSellerTypeEnumregionstringsource_locationobjecthas_accidentbooleanis_new_vehiclebooleanis_verifiedbooleanstatusVehicleStatusEnumis_availablebooleanfirst_seen_atstringlast_seen_atstringthumbVehiclePhotophotosarrayphotos_countintegerhas_valuationbooleanhas_llm_analysisbooleananalysisobject
Detail — GET /apix/api/vehicles/{id}/ — adds 23 more:
generationstringprice_originalstringprice_original_currencystringoriginal_msrpstringengine_ccintegerseat_countintegerdrive_typeDriveTypeEnumhas_simple_repairbooleanhas_recallbooleanrecall_fulfilledbooleanwarranty_typestringinspection_passedbooleanowner_countintegeris_undervaluedbooleanvaluation_scorenumberfeaturesarraydescriptionstringlisting_urlstringlisting_idstringvinstringvehicle_nostringavailability_checked_atstringstatus_changed_atstring
Abbreviated example:
{
"id": "0193f2c1-...",
"source_code": "encar",
"brand_name": "BMW",
"model_name": "320i",
"trim": "M Sport",
"year": 2021,
"price_usd": 28400,
"price_original": "38900000",
"price_original_currency": "KRW",
"mileage": 45000,
"fuel_type": "gasoline",
"transmission": "automatic",
"has_accident": false,
"listing_url": "https://...",
"photos": [{ "url": "https://cdn.carapis.com/..." }],
"first_seen_at": "2026-09-28T11:04:22Z",
"is_available": true
}Which sources you can actually query is answered by GET /apix/api/sources/ with your API key — it is the list your account can pull today, and it is the one to trust over any page on this site.
The aggregated sold-price history and per-model market trends are what make Classic.com uniquely valuable: instead of one venue’s data, you get the collector market’s consolidated price record — delivered as structured fields. Because it indexes other sources, completeness depends on what each underlying venue publishes.
API Quick Start
Python
import requests
resp = requests.get(
"https://api.carapis.com/v2/listings",
params={"source": "classic-com", "limit": 20},
headers={"Authorization": f"Bearer {API_KEY}"},
)
for car in resp.json()["results"]:
print(car["make"], car["model"], car["year"], car["price"])Get an API key at my.carapis.com and see the full API reference. Pricing is on the pricing page .
Use Cases
- Pricing intelligence — cross-platform sold-price history and per-model trends power collector valuation for dealers and specialists.
- Market research — track the whole collector market in one feed instead of stitching venues together. See market research.
- Import / export — model-level price benchmarks help cross-border buyers value rare vehicles. See import & export.