Used and new car market research
Autotraderエンドポイントを使えば、「Used and new car market research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
翻訳作業中です。 日本語訳を準備中のため、このページは一時的に英語で表示されます。
マーケットプレイス＆リテール稼働中エンドポイント 3件apiKey
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.
エンドポイントファミリー
3
ドキュメント化されたパラメータ
20
サンプル数
3
ライブカタログスナップショット
Autotraderのカバレッジ
稼働エンドポイント
3
メソッド
GET
必須パラメータ
5
スキーマ参照
3
Dealer1
Search1
Vehicle1
{
"platform": "Autotrader",
"endpoint": "autotrader-search",
"method": "GET",
"path": "/autotrader/search",
"auth": "apiKey"
}ユースケース
Autotraderに適したワークフロー
Search Autotrader vehicle listings and get normalized vehicle spec, dealer profiles, and current dealer inventory as structured JSON.
Price and mileage monitoring
Autotraderエンドポイントを使えば、「Price and mileage monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Dealer inventory tracking
Autotraderエンドポイントを使えば、「Dealer inventory tracking」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
Crawloraによるこのプラットフォームの処理方法
以下の数値はすべて、稼働中のAutotraderエンドポイントカタログから取得しています（エンドポイント3件、ドキュメント化されたリクエストパラメータ20個、公開レスポンススキーマ3件）。DocsとPlaygroundが参照しているカタログと同じものです。
ドキュメント化されたエンドポイント
Autotraderのエンドポイントは3件、3つのリクエストファミリーに分類されています（Dealer、Search、Vehicle）。
公開されたリクエスト仕様
これらのAutotraderエンドポイントには20個のリクエストパラメータがドキュメント化されており、うち5個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
判明しているレスポンス構造
3件のAutotraderエンドポイントのうち3件が実際のサンプルレスポンスを、3件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
ドキュメント化されたエラー
Autotraderのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、500、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
エージェントから呼べるMCPツール
Autotraderのエンドポイントは3個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
統合前にAPIで収集できるデータを把握
1エンドポイント
Dealer
/autotrader/dealer/{id}
GETapiKey
1エンドポイント
Search
/autotrader/search
GETapiKey
1エンドポイント
Vehicle
/autotrader/vehicle/{id}
GETapiKey
エンドポイントカタログ
Autotrader APIエンドポイント
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.
レスポンスに関する注記
- `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ツール autotrader_search
query:queryzip:queryradius:query他13件
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).
レスポンスに関する注記
- `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ツール 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.
レスポンスに関する注記
- `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ツール autotrader_dealer
id:pathx-api-key:header
関連API
マーケットプレイス＆リテールのその他のカバレッジ
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.
Autotraderのスクレイピング方法
8ステップで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.
- ステップ 1
Search vehicle listings
Send a make, model, and location to /autotrader/search for normalized vehicle summaries — price, year, mileage, colors, and transmission.
- ステップ 2
Get listing detail
Pass a listing id to /autotrader/vehicle for the full vehicle spec, including drivetrain and fuel type.
- ステップ 3
Look up a dealer
Pass a dealer id to /autotrader/dealer for the dealer profile plus a first page of current inventory.
- ステップ 4
Monitor over time
Re-run searches on a schedule to track price, mileage, and inventory changes.
- ステップ 5
Send Autotrader codes for make and model
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.
- ステップ 6
Take ids from the right URL segment
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.
- ステップ 7
Combine the three routes
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.
- ステップ 8
Expect vehicle pages to 503 on shape drift
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.
エージェントスキル
コーディングエージェントから Autotrader のデータを利用
Crawlora のエージェントスキルをインストールすると、スクレイパーを書かずに、ドキュメント化された API 経由で Autotrader のデータを JSON として取得できます。Autotrader に対応するスキル:
Used-car market comparison
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-comparisonUsed-car price history analysis
Analyze 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-analysisReal estate & auto research
Researches 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-research
FAQ
Autotraderのスクレイピング：よくある質問
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.
Which Autotrader ids does each route take?
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}.
Can I search by model without a make?
No. The model parameter requires make, and both take Autotrader's uppercase codes.