Skip to content

Cars.com Vehicle Listings via Scraping API

Cars.com pages mix server-rendered listing data with JavaScript-driven content, and they sit behind bot detection that can block naive requests.

OUTPUT FORMATSHTMLJSONMarkdown

A managed scraping API lets you send a Cars.com URL and receive rendered HTML or structured JSON without maintaining your own headless browser fleet or proxy pool. This guide explains what the API returns, which request controls matter for vehicle data, how credits are consumed, and where the practical limits sit so you can decide whether it fits your pipeline.

What the API does with a Cars.com URL

You pass a Cars.com listing or search URL to the endpoint along with your API key. The service renders the page in a real headless browser, rotates proxies, and attempts to bypass bot detection before returning the post-render HTML. If you supply extraction rules, the response can come back as parsed JSON instead of raw markup.

The captured field list for a Cars.com listing covers make, model, year, mileage, listing price, MSRP, VIN, dealer name, location, condition, and the full photo gallery. That set is enough to build a pricing monitor, a dealer inventory map, or a vehicle specification dataset without writing a per-field parser for every page layout.

Three workflows this API supports

Vehicle specification extraction. Pull make, model, year, and condition into a structured table for competitor analysis or lead generation. The API returns the rendered page, and your extraction rules select the fields you need.

Dealer inventory mapping. Aggregate which dealers list which makes and models across markets. This is public listing data; the API is not designed for bulk extraction of dealer contact details.

Vehicle pricing data. Collect listing price and MSRP across a set of Cars.com pages to compare pricing positions. Pair this with a scheduled job so the dataset reflects current listings rather than a one-off snapshot.

Request controls that matter for Cars.com

The API exposes a small set of parameters that change how a Cars.com request is handled. The table below maps each control to its effect and its credit cost where the captured contract specifies one. Treat the credit figures as the published contract for this API, not as estimates.

ControlWhat it doesCredit effect
render_jsRuns the page in a headless browser and returns post-render HTML5 credits per successful request when enabled
stealth_proxyRoutes through premium proxies to reduce blocking10 credits without JS rendering; 25 credits with JS rendering
country_codeRoutes through a residential IP in the specified countryNo separate credit line captured
extract_rulesMaps CSS selectors to field names and returns parsed JSONNo separate credit line captured
ai_extract_rulesNatural-language extraction spec returning parsed JSONNo separate credit line captured
screenshotCaptures a full-page screenshotNo separate credit line captured

A base request starts at 1 credit. Credits are valid for one month and do not roll over. Concurrency is capped per plan rather than per target, so the number of simultaneous requests is the practical throughput limit.

Decision checklist before you build

Use this checklist to decide whether the managed API fits your Cars.com workflow.

  • Do you need rendered JavaScript output, or is the listing data present in the initial HTML? If the latter, a plain HTTP request may be enough and cheaper.
  • Will you hit bot detection at your target volume? If yes, the stealth proxy and JS rendering combination is the relevant configuration, at 25 credits per successful request.
  • Do you need structured JSON, or will you parse HTML yourself? extract_rules or ai_extract_rules returns parsed JSON and removes a parsing layer.
  • Does your content vary by country? country_code routes through a residential IP in that country.
  • What is your monthly request budget? Multiply your expected request count by the credit cost of your chosen configuration and compare against the plan's credit allowance.
  • Do you need more than the plan's concurrency? Concurrency is the throughput ceiling, not a per-target rate limit.

Worked example: one Cars.com listing request

Suppose you want the price, mileage, VIN, and dealer for a single listing. You send the listing URL with render_js=true and stealth_proxy=true, plus extract_rules mapping your field names to the page's CSS selectors. The request consumes 25 credits if it succeeds, because premium proxies with JS rendering are priced at that rate. The response is parsed JSON containing the fields you mapped.

If the same request omits stealth_proxy, it consumes 5 credits for JS rendering and may be blocked depending on the target's defenses. If it omits render_js as well, it consumes 1 credit and returns the initial HTML, which may not contain the listing data.

This example uses only the parameter names and output behavior described in the API contract. It does not assume a specific selector for any Cars.com page, because selectors change as the site's markup changes.

Three different failure modes

A failed request can mean three different things, and the fix differs for each.

Concurrency limit reached. The API enforces a maximum number of simultaneous requests per plan. If you exceed it, requests queue or are rejected. The fix is to reduce parallelism or move to a plan with higher concurrency.

Target-side throttling. Cars.com may throttle aggressive request patterns even when your API concurrency is within limits. The fix is to space out requests or use multiple sessions, as the API's own guidance suggests.

Anti-bot blocking. The target may serve a challenge page instead of the listing. The fix is to enable stealth_proxy and render_js, which routes through premium proxies and a real browser. If blocking persists at that configuration, the target's defenses have changed and the request pattern needs review.

Plans and credit allowances

The API is sold on monthly plans that bundle API credits, concurrency, JavaScript rendering, rotating and premium proxies, geotargeting, screenshots and extraction rules, and support levels. The captured plan table lists seven tiers from a hobby plan through enterprise tiers, with credit allowances rising from 75,000 to 120,000,000 per month and concurrency from 25 to 900 simultaneous requests. All tiers include JavaScript rendering, proxies, geotargeting, and extraction rules; priority support, a dedicated account manager, and team management appear only on the business and enterprise tiers.

Prices are exclusive of VAT. Credits are valid for one month and do not roll over. The plan table is a dated reference; check the current pricing page before committing to a tier.

Data handling and compliance

The service states that it does not collect or store personal data from scraped sites unless the user explicitly requests it. It also states that it handles proxy rotation and headless browser rendering to reduce blocking risk. These are the provider's stated positions; your own obligations under GDPR, CCPA, or the target site's terms remain yours to assess. Cars.com listing data is public inventory and pricing information, but dealer contact details and any personal data in listings should be handled according to your jurisdiction's rules.

Captured plan comparison (dated reference)
PlanMonthly priceAPI creditsConcurrent requestsPriority supportAccount managerTeam management
Hobby$1975,00025Not includedNot includedNot included
Freelance$49250,00050Not includedNot includedNot included
Startup (Recommended)$991,000,000100Not includedNot includedNot included
Business$2493,000,000200IncludedIncludedIncluded
Business +$5998,000,000400IncludedIncludedIncluded
Enterprise 14$99914,000,000500IncludedIncludedIncluded
Enterprise 24$1,59924,000,000600IncludedIncludedIncluded
Enterprise 41 (Recommended)$2,39941,000,000700IncludedIncludedIncluded
Enterprise 69$3,59969,000,000800IncludedIncludedIncluded
Enterprise 120$5,799120,000,000900IncludedIncludedIncluded

All prices are exclusive of VAT. Credits are valid for one month and do not roll over. This table reflects the captured plan data and should be checked against the current pricing page.

Frequently asked questions

Can I scrape Cars without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL. You still need to run that snippet somewhere, but you do not have to write the request logic from scratch.

How do I handle JavaScript when scraping Cars?

Pass render_js=true on the request. The service runs the page in a real headless browser, executes the JavaScript server-side, and returns the post-render HTML. This costs 5 credits per successful request when enabled.

Can I scrape Cars from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when content varies by geography.

What's the rate limit for scraping Cars?

The API has concurrency limits per plan, not per-target rate limits. If the target throttles aggressive patterns, space out requests or use multiple sessions.

How do I get structured JSON from Cars?

You have two routes to a JSON response. The first is extract_rules, where you pair each field name you want with the CSS selector that targets it on the page. The second is ai_extract_rules, where you describe the fields you want in plain language and let the service resolve them. Either way, the response body arrives as parsed JSON rather than raw HTML.

Which programming languages can I use to scrape Cars?

Any. SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java. Plain cURL works too. Pick whatever your stack already uses.