Skip to content

Vehicle Listings and Pricing Data via API

Vehicle-listing sites are built to resist automated reading: JavaScript-rendered inventories, rotating bot checks and per-region pricing.

OUTPUT FORMATSHTMLJSONMarkdown

A managed scraping API moves that work off your plate. You send a listing URL; the service renders the page, rotates proxies, handles bot detection and returns HTML you can parse — or structured JSON if you supply extraction rules. This page covers what the API returns, how requests are priced in credits, and where the plan tiers differ, so you can size a pipeline before writing code.

What a vehicle-listing call returns

A single request against a public vehicle-listing page can return the fields buyers and analysts usually need: make, model, year, trim, mileage, price, VIN, body style, fuel economy, dealer information and the photo gallery. The same call can cover dealer inventory pages and marketplace listings, which makes it usable for regional price comparison, catalog building and risk or insurance workflows where accident history, prior-owner counts and service records are publicly exposed.

Three jobs dominate real vehicle-data work: comparing inventory across regions, extracting specifications such as trim and drivetrain, and collecting accident or service history where a site publishes it. The API does not invent fields a page does not show — if a value is not rendered on the public page, no extraction rule will produce it.

Request inputs and what each one changes

The request is a GET call with your API key and the target listing URL. Beyond that, a small set of parameters controls behaviour:

  • render_js — runs the page in a real headless browser and returns post-render HTML. Use it when the listing grid or price is injected by JavaScript.
  • stealth_proxy — routes the request through premium proxies when a target site is aggressive about blocking.
  • country_code — geotargets the request; the platform routes through 200+ countries and territories (40+ on classic proxies), which matters when a marketplace shows different inventory or currency per region.
  • extract_rules — CSS or XPath selectors that pull specific elements into structured output.
  • ai_extract_rules — a natural-language description of the fields you want, returned as structured JSON without per-site selectors.
  • screenshot — captures a full-page image, useful as a visual record of a listing before it expires.

A dashboard request builder lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL, so you can test a target before committing to a parser.

HTML or JSON: choosing your output

By default you get rendered HTML back, ready for your own parser. If you supply extract_rules or ai_extract_rules, the response is structured JSON keyed to the fields you named. The JSON path removes per-site selector maintenance but depends on the page actually rendering the values you asked for; the HTML path gives you full control but puts parsing and selector upkeep on your side.

A practical split: use ai_extract_rules while you are still learning a new marketplace's markup, then move stable, high-volume targets to CSS or XPath extract_rules once the field set settles. Screenshots are a separate output and are best treated as an audit trail rather than a data source.

How a vehicle-listing request is priced in credits

Credits are consumed per successful request, and the cost depends on which features you enable:

  • Base request: starts at 1 credit.
  • JavaScript rendering: +5 credits per successful request that enables it.
  • Premium proxies: 10 credits with JS rendering disabled, 25 credits with JS rendering enabled.

API credits are valid for one month and do not roll over. Concurrent requests are capped by plan.

Worked example: a batch of 1,000 listing pages that need JavaScript rendering and premium proxies costs 25,000 credits (25 per page). The same 1,000 pages with JavaScript rendering but classic proxies costs 5,000 credits (5 per page). If a target renders server-side and does not need premium proxies, the same batch costs 1,000 credits. Budget from the most expensive path your targets actually require, not the cheapest.

Plan tiers and what changes between them

Standard plans include JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules from the entry tier upward. What changes across tiers is the monthly credit allowance and the concurrent-request ceiling. Priority email support, a dedicated account manager and team management appear only on the Business tier and above.

A quick way to size a plan: divide your monthly page volume by the per-page credit cost of your heaviest target, then check that the result fits inside a tier's credit allowance with headroom for retries. Concurrency matters separately — if your pipeline fans out across many dealer sites at once, the concurrent-request cap, not the credit total, may be the binding limit.

Three failure modes and how to tell them apart

Most disappointing vehicle-data runs fall into one of three buckets, and each has a different fix:

  1. Empty or skeleton HTML — the page rendered but the listing data was injected by JavaScript. Fix: enable render_js.
  2. Block page or CAPTCHA — the request was identified as automated. Fix: enable stealth_proxy, and consider country_code if the block is region-specific.
  3. Rendered page but missing fields — the values are not where your selectors expect, or the page genuinely does not publish them. Fix: switch to ai_extract_rules to confirm the field exists, then lock in extract_rules.

Checking which bucket you are in before changing parameters saves credits: a render_js toggle on a page that is actually blocked will not help, and a stealth_proxy toggle on a page that simply needs rendering is wasted spend.

Legal and compliance checks before you deploy

Public-facing pages can usually be scraped, but review the target site's terms of service before deploying and avoid post-login content. The platform does not collect or store personal data from scraped sites unless the user explicitly requests it, and it describes itself as GDPR and CCPA compliant. Those are platform-level statements; your own obligations as a data controller depend on what you collect and why, so treat the compliance check as a step in your pipeline design rather than a box ticked by the vendor.

Frequently asked questions

Is scraping vehicle data legal?

Public-facing pages can usually be scraped, but review the target site's terms of service before deploying and avoid post-login content. Legality depends on the site, the jurisdiction and what you do with the data, so this is a design input rather than a one-time check.

What data can I extract from vehicle data?

Whatever the public page actually displays. Two routes turn it into structured JSON: extract_rules, where you point CSS selectors at the elements you want, or ai_extract_rules, where you describe the fields in plain language and the service maps them for you. Typical targets are make, model, year, trim, mileage, price, VIN, body style, fuel economy, dealer info and the image gallery.

How do I start scraping vehicle data?

Sign up, grab your API key, and send a GET request with the target URL. The service renders the page, rotates proxies and returns the data. 1,000 free credits are available to test with.

Will I get blocked when scraping vehicle data?

Residential proxies rotate and a real headless browser is used, so requests resemble normal traffic. If a target gets aggressive, enable stealth_proxy on the request.

Can I scrape vehicle data 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. No-code workflows via n8n are also supported.

How do I handle JavaScript when scraping vehicle data?

Pass render_js=true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and you get the post-render HTML back.

How many credits does a single vehicle-listing request cost?

A base request starts at 1 credit. JavaScript rendering adds 5 credits per successful request. Premium proxies cost 10 credits with JS rendering disabled, or 25 credits with it enabled. Credits are valid for one month and do not roll over.

What is the difference between extract_rules and ai_extract_rules?

extract_rules uses CSS or XPath selectors you write, which is precise but needs maintenance when a site's markup changes. ai_extract_rules takes a natural-language description of the fields you want and returns structured JSON without per-site selectors, which is faster to set up on unfamiliar marketplaces.