Used and new car market research
Use Autotrader endpoints to turn used and new car market research into repeatable API requests with documented inputs and JSON responses.
翻译进行中。 该页面的简体中文翻译正在准备中，暂时以英文内容显示。
电商与零售3 active endpointsapiKey
Autotrader Scraper API
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.
Endpoint families
3
Documented params
20
Examples
3
Live catalog snapshot
Autotrader coverage
Active endpoints
3
Methods
GET
Required params
5
Schema refs
3
Dealer1
Search1
Vehicle1
{
"platform": "Autotrader",
"endpoint": "autotrader-search",
"method": "GET",
"path": "/autotrader/search",
"auth": "apiKey"
}Use cases
Workflows that fit Autotrader
Search Autotrader vehicle listings and get normalized vehicle spec, dealer profiles, and current dealer inventory as structured JSON.
Price and mileage monitoring
Use Autotrader endpoints to turn price and mileage monitoring into repeatable API requests with documented inputs and JSON responses.
Dealer inventory tracking
Use Autotrader endpoints to turn dealer inventory tracking into repeatable API requests with documented inputs and JSON responses.
Managed execution
How Crawlora handles this platform
Every figure below is read from the live Autotrader endpoint catalog — 3 endpoints, 20 documented request parameters, and 3 published response schemas — the same catalog Docs and Playground run against.
Documented endpoint coverage
3 documented Autotrader endpoints, grouped into 3 request families — Dealer, Search and Vehicle.
Published request surface
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.
Known response shape
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.
Documented failure modes
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.
Agent-callable MCP tools
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.
Coverage map
Know what the API can collect before integrating
1 endpoints
Dealer
/autotrader/dealer/{id}
GETapiKey
1 endpoints
Search
/autotrader/search
GETapiKey
1 endpoints
Vehicle
/autotrader/vehicle/{id}
GETapiKey
Endpoint catalog
Autotrader API endpoints
GETapiKeyexample
/autotrader/searchSearch Autotrader vehicle listings
Searches Autotrader for new and used car listings, returning vehicle summaries (make, model, trim, year, mileage, pricing, images) plus the total matching count.
Response notes
- `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
query:queryzip:queryradius:query+13 more
GETapiKeyexample
/autotrader/vehicle/{id}Get Autotrader vehicle listing detail
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).
Response notes
- `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
id:pathx-api-key:header
GETapiKeyexample
/autotrader/dealer/{id}Get Autotrader dealer profile
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.
Response notes
- `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
id:pathx-api-key:header
Related APIs
More 电商与零售 coverage
Marketplaces & Retail
Reverb
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
Amazon
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
eBay
Build resale, pricing, and marketplace workflows from structured eBay data.
How to scrape Autotrader
Extract Autotrader data in 4 steps
Crawlora's Autotrader endpoints return vehicle search results, listing detail, and dealer profiles as normalized JSON with one API key — no HTML parsing required.
- Step 1
Search vehicle listings
Send a make, model, and location to /autotrader/search for normalized vehicle summaries — price, year, mileage, colors, and transmission.
- Step 2
Get listing detail
Pass a listing id to /autotrader/vehicle for the full vehicle spec, including drivetrain and fuel type.
- Step 3
Look up a dealer
Pass a dealer id to /autotrader/dealer for the dealer profile plus a first page of current inventory.
- Step 4
Monitor over time
Re-run searches on a schedule to track price, mileage, and inventory changes.
FAQ
Scraping Autotrader: common questions
How do I search Autotrader listings with an API?
Send a make, model, and location to Crawlora's /autotrader/search endpoint and get normalized vehicle summaries as structured JSON.
Does the Autotrader API require an account or API key?
No Autotrader account or API key is required from the caller — only your Crawlora API key.
Can I get a dealer's current inventory?
Yes — /autotrader/dealer returns the dealer profile (name, phone, address, rating, website) plus a first page of that dealer's current listings.