Used and new car market research
Mit Autotrader-Endpunkten verwandelst du used and new car market research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn public Autotrader listings into structured vehicle data — search by make, model, and location, get a full vehicle spec (trim, mileage, colors, transmission, fuel type, drivetrain) for one listing, and pull a dealer's profile plus current inventory. Credential-free.
Search Autotrader vehicle listings and get normalized vehicle spec, dealer profiles, and current dealer inventory as structured JSON.
Endpunkt-Familien
3
Dokumentierte Parameter
20
Beispiele
3
Live-Katalog-Snapshot
Aktive Endpunkte
3
Methoden
GET
Pflichtparameter
5
Schema-Referenzen
3
{
"platform": "Autotrader",
"endpoint": "autotrader-search",
"method": "GET",
"path": "/autotrader/search",
"auth": "apiKey"
}Use Cases
Search Autotrader vehicle listings and get normalized vehicle spec, dealer profiles, and current dealer inventory as structured JSON.
Mit Autotrader-Endpunkten verwandelst du used and new car market research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Autotrader-Endpunkten verwandelst du price and mileage monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Autotrader-Endpunkten verwandelst du dealer inventory tracking in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Autotrader-Endpunktkatalog — 3 Endpunkte, 20 dokumentierte Request-Parameter und 3 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
3 documented Autotrader endpoints, grouped into 3 request families — Dealer, Search and Vehicle.
20 request parameters are documented across those Autotrader endpoints, 5 of them required — the full input contract is public before you write any integration code.
3 of the 3 Autotrader endpoints ship a recorded example response, and 3 carry a documented response schema — you can code against the real JSON before the first request.
Autotrader endpoints document their error responses (400, 404, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
3 hosted MCP tools back the Autotrader endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/autotrader/dealer/{id}
/autotrader/search
/autotrader/vehicle/{id}
Endpunktkatalog
/autotrader/searchSearches Autotrader for new and used car listings, returning vehicle summaries (make, model, trim, year, mileage, pricing, images) plus the total matching count.
Hinweise zur Response
- `total_count` reflects Autotrader's full matching-result count for the applied filters, not just `len(vehicles)`. - An invalid `condition`, `body_style`, or `seller_type` value returns `400` before any upstream request is made. - A search with no matching listings returns `200` with `"vehicles": []` and `total_count: 0`, not an error. - `pricing.no_price_label` (e.g. `"Contact Dealer For Price"`) is set instead of a numeric price when the dealer requires direct contact for pricing. - `stats` reports price and model-year aggregates (min/average/max) across the FULL matching result set for the applied filters, not just the returned page — useful for market-research callers who want the shape of the whole matching inventory. It is omitted when Autotrader's page does not carry this aggregate for the request.
MCP-Tool autotrader_search
/autotrader/vehicle/{id}Returns an Autotrader vehicle listing: full vehicle spec (make, model, trim, mileage, colors, transmission, fuel type, engine, images, pricing), the full listing description, and seller detail (dealership or private seller).
Hinweise zur Response
- `id` must be numeric; a non-numeric value returns `400` before any upstream request is made. - A listing id that is well-formed but no longer exists (sold, removed, or never existed) returns `404`, not an empty `200`. - `dealer` is omitted when Autotrader's page does not carry a resolvable seller record for the listing (parser drift or an incomplete listing). - `pricing.no_price_label` (e.g. `"Contact Dealer For Price"`) is set instead of a numeric price when the dealer requires direct contact for pricing. - `similar_listings` is a list of vehicle summaries (the same shape as a search result, not full detail) for other listings Autotrader surfaces as similar on the same page. It is omitted when Autotrader's page does not carry a similar-listings shelf for this vehicle.
MCP-Tool autotrader_vehicle
/autotrader/dealer/{id}Returns an Autotrader dealer profile (name, phone, address, rating, website) plus a first page of the dealer's own current inventory as vehicle summaries and the dealer's total listing count.
Hinweise zur Response
- `id` must be numeric; a non-numeric value returns `400` before any upstream request is made. - A dealer id that is well-formed but has no resolvable dealer record returns `404`, not an empty `200`. - `inventory` is a first batch of the dealer's own current listings (the page Autotrader itself renders), not the dealer's entire lot. `total_count` reports the dealer's true current listing count, which may be larger than `len(inventory)`. - `is_private_seller` is `true` for a private-individual seller profile rather than a dealership.
MCP-Tool autotrader_dealer
Verwandte APIs
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
So scrapst du Autotrader
Crawlora's Autotrader endpoints return vehicle search results, listing detail, and dealer profiles as normalized JSON with one API key — no HTML parsing required. Autotrader's search, vehicle and dealer routes use three different identifiers and inputs, and the documented contract matters more than the example call: make and model take Autotrader's own codes, and a model requires a make.
Send a make, model, and location to /autotrader/search for normalized vehicle summaries — price, year, mileage, colors, and transmission.
Pass a listing id to /autotrader/vehicle for the full vehicle spec, including drivetrain and fuel type.
Pass a dealer id to /autotrader/dealer for the dealer profile plus a first page of current inventory.
Re-run searches on a schedule to track price, mileage, and inventory changes.
make takes Autotrader's code (for example TOYOTA, HONDA or BMW) and model takes a model code such as CAMRY, which requires make. A ZIP must be five digits and radius is in miles, so normalize user input before the call.
The vehicle route takes the numeric segment of a /cars-for-sale/vehicle/{id} URL, and the dealer route takes the numeric segment of a /car-dealers/{id} URL. They are different id spaces, so store which one you hold.
Search returns vehicle summaries (make, model, trim, year, mileage, pricing, images) plus a total matching count. The vehicle route adds the full specification, listing description and seller detail, and the dealer route adds a profile and a first page of that dealer's inventory with a total listing count.
On 2026-10-30 /autotrader/vehicle/788444963 answered 503 autotrader returned a page without a __NEXT_DATA__ payload, while /autotrader/dealer/670936 returned AutoNation Toyota South Austin with rating 5 from 15,166 ratings and 25 inventory rows.
Agent Skills
Installiere einen Crawlora Agent Skill, und dein Agent ruft Autotrader-Daten als JSON über die dokumentierte API ab, ohne einen Scraper zu schreiben. Diese Skills decken Autotrader ab:
Compare used-car asking prices with matched local listings through Crawlora. Use for a vehicle shortlist, a comparable-listing price range, or…
npx skills add github.com/Crawlora-org/crawlora-skills --skill used-car-market-comparisonAnalyze observed used-car listing price changes through Crawlora stored vehicle histories and selected live listings. Use for a dated price-change…
npx skills add github.com/Crawlora-org/crawlora-skills --skill used-car-price-history-analysisResearches homes and used cars via the Crawlora API — Zillow and Redfin property search/estimates/market trends, plus CarMax, Autotrader, and…
npx skills add github.com/Crawlora-org/crawlora-skills --skill real-estate-autos-researchFAQ
Send a make, model, and location to Crawlora's /autotrader/search endpoint and get normalized vehicle summaries as structured JSON.
No Autotrader account or API key is required from the caller — only your Crawlora API key.
Yes — /autotrader/dealer returns the dealer profile (name, phone, address, rating, website) plus a first page of that dealer's current listings.
The vehicle route takes the listing id from a /cars-for-sale/vehicle/{id} URL and the dealer route takes the dealer id from /car-dealers/{id}.
No. The model parameter requires make, and both take Autotrader's uppercase codes.