CarSensor Used Cars Scraper

Collect publicly available CarSensor (carsensor.net) used-car listings in Japan as clean, structured records. Feed the actor a brand/model listing page and/or direct vehicle detail pages; it returns one rich record per vehicle — price, mileage, spec sheet, dealer and equipment.

Input

field	description
startUrls	CarSensor URLs to scrape. Listing pages (e.g. https://www.carsensor.net/usedcar/bTO/s241/index.html) — the actor follows every detail link on them, plus pagination. Direct detail pages (e.g. https://www.carsensor.net/usedcar/detail/AU6908770566/index.html) — scraped straight away. You can mix both.
maxItems	Cap on total vehicles returned (0 = no cap).
maxPagesPerListing	Cap on paginated listing pages followed per start URL (0 = no cap).
proxyConfiguration	Uses Apify Residential (Japan) by default — no external proxy key needed.

What you get (one record per vehicle)

field	description
id	CarSensor vehicle code (AU+digits)
url	detail page URL
brand / model / grade	e.g. Toyota / C-HR / Hybrid 1.8 G
year	model year
price_total_jpy / price_body_jpy	total payment price and vehicle body price, in yen
currency	always JPY
mileage_km	odometer reading
inspection	shaken (vehicle inspection) status
repair_history	boolean — accident/repair history disclosed
displacement_cc	engine displacement
transmission	e.g. CVT
fuel	fuel grade
drive	2WD / 4WD
color	exterior colour
seats	seating capacity
body_type	e.g. SUV
region	prefecture
dealer / dealer_address	selling dealer name and address
warranty	warranty terms
image_url / image_count	lead photo and gallery size
features / feature_count	fitted-equipment list
scraped_at	UTC timestamp

How it works

CarSensor detail pages carry no schema.org markup, so the scraper reads the page's own stable, site-wide CSS structure directly: the summary tiles (year, mileage, repair history, inspection, region, warranty), the basic- and detailed-spec tables (th/td label→value pairs), the breadcrumb trail (brand/model), and the heading (grade + fitted equipment). This is resilient to cosmetic markup changes, unlike scraping off hashed utility class names. Listing pages are parsed for their detail links and the site's own pagination link, which are then followed. Requests use a residential proxy for reliable access; you only supply the URLs.

Pricing

Pay per result — you are charged once per vehicle record written to the dataset. Compute runs on your own Apify account.

Notes

This tool collects publicly available vehicle listing data for research and aggregation.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.