Japan Used Cars (carsensor.net)

Japanese used-car listings — price, year, mileage, repair history, inspection status and selling-dealer info — from carsensor.net, one of Japan's largest used-car marketplaces, in a clean English schema.

This Actor searches carsensor.net's public used-car listings by maker and prefecture and returns each vehicle as English-schema JSON: maker (Japanese + English), model and grade, base vehicle price and total payment in JPY, first-registration year, mileage in km, engine displacement, transmission, repair-history flag (修復歴), inspection (車検) expiry, color, body type, and the selling dealer's business name, city and prefecture. With detailFetch it adds drive type, engine type (hybrid/EV/…), steering side, seats, doors and the dealer's business address from each vehicle's detail page. Optional client-side filters narrow by model keyword, price window (万円) and year window.

Japan's used-car market is a major export source (JDM icons, hybrids, kei trucks), but carsensor.net is Japanese-only — invisible to most international tooling. This Actor is the bridge.

Unofficial tool. Not affiliated with or endorsed by Recruit Co., Ltd. or carsensor.net. It collects publicly available data only (no login, no paywall), politely (strictly serial requests, ≥1.2 s apart, hard per-run budget, no block evasion), and extracts factual data only — vehicle facts and dealer business identity; no review content, no dealer marketing prose, no personal data of any kind (relevant e.g. under GDPR: no personal data is collected or processed). Users are responsible for ensuring their own use of the data complies with the source site's terms and applicable law.

---

Quick start — verified input

Copy-paste this into the Actor's input (JSON tab) or pass it via API — it was run successfully on 2026-09-02 (10 Toyota vehicles from Osaka dealers, list data, ~15 seconds):

{
  "prefecture": "Osaka",
  "maker": "Toyota",
  "maxItems": 10
}

Common input mistakes

Wrong	Right	Why
"prefecture": "Osaka-shi" / "Nagoya" / "Kansai"	"prefecture": "Osaka" / "Aichi" / one prefecture at a time	prefecture must be one of the 47 prefectures (English name, dropdown); regions and cities are not accepted.
"prefecture": "大阪府" or "27" (via API)	"prefecture": "Osaka"	The platform checks the 47 English names before the run starts; other spellings are rejected with the valid list.
"maker": "Toyota Prius"	"maker": "Toyota", "model": "プリウス"	maker is the brand only (dropdown); the model goes in model (Japanese matches best).
"maker": "Benz" (via the UI dropdown)	"maker": "Mercedes-Benz"	The dropdown lists the supported makers by English name; via API aliases such as Benz / VW / トヨタ / bTO are accepted.
"priceMax": 1500000	"priceMax": 150	Prices are in 万円 (10,000 JPY units): 150 = ¥1,500,000.
"yearMin": "2018"	"yearMin": 2018	Numbers are numbers in JSON — the platform rejects a numeric string before the run starts.

Every invalid value stops the run immediately (before any upstream request) with a message that names the field and lists the valid values. Fields with a fixed list of values are validated by the Apify platform before the run even starts.

Empty results?

A run that finishes with items: 0 and complete: true is not an error. Typical causes: a maker with no dealers in the chosen prefecture (carsensor answers HTTP 404 for that list page — the actor logs it and returns 0 vehicles), a model keyword written in romaji where the site uses katakana (try プリウス instead of Prius), or tight price / year windows with a small maxApiRequests (filtering is client-side — raise the budget). Widen the query and re-run.

---

Who is this for?

• Used-car exporters & overseas dealers — source JDM vehicles by maker, model, price and repair history before they hit the auctions; the repair-history flag (修復歴) and inspection status are exactly the fields export buyers check first.
• Market & price analysis — used-car price levels by model, year and mileage across all 47 prefectures; a public-listing alternative to closed auction-sheet data.
• Automotive SaaS & valuation tools — feed live Japanese retail asking prices into pricing models.
• Data teams — a stable English schema over a Japanese-only source.

Sample output (dataset item)

{
  "carName": "トヨタ プリウスα G 5ニンノリ",
  "maker": "トヨタ",
  "makerEn": "Toyota",
  "model": "プリウスα",
  "grade": "G 5ニンノリ",
  "priceJpy": 1050000,
  "totalPaymentJpy": 1173000,
  "year": 2016,
  "mileageKm": 53000,
  "displacementCc": 1800,
  "transmission": "その他AT",
  "repairHistory": false,
  "inspectionUntil": null,
  "inspectionNote": "車検整備付",
  "color": "パールマイカ",
  "bodyType": "ミニバン",
  "driveType": "2WD",
  "engineType": "ハイブリッド",
  "steering": "right",
  "seatingCapacity": 5,
  "doors": 5,
  "dealerName": "ネッツトヨタニューリー北大阪（株） 千里店",
  "dealerPrefecture": "大阪府",
  "prefectureEn": "Osaka",
  "prefectureCode": "27",
  "dealerCity": "吹田市",
  "dealerAddress": "大阪府吹田市山田西１－３６－１０",
  "url": "https://www.carsensor.net/usedcar/detail/AU7231736290/index.html",
  "detailFetched": true,
  "source": "カーセンサーnet (carsensor.net)",
  "sourceUrl": "https://www.carsensor.net/",
  "license": "Publicly available data — unofficial tool; users are responsible for compliance with the source site's terms",
  "retrievedAt": "2026-08-25T13:10:00Z"
}

Input reference

{
  "prefecture": "Osaka",
  "maker": "Toyota",
  "model": "プリウス",
  "yearMin": 2016,
  "priceMax": 150,
  "detailFetch": true,
  "maxItems": 50,
  "maxApiRequests": 60
}

• prefecture (required): English name of one of the 47 prefectures exactly as in the dropdown ("Osaka", "Tokyo" …). The Apify platform validates this list before the run starts, so "大阪府", "27" or "osaka-fu" are rejected immediately with the list of valid values. Cities are not prefectures — "Nagoya" is rejected; use "Aichi".
• maker (optional, dropdown): Toyota, Lexus, Nissan, Honda, Mazda, Subaru, Suzuki, Mitsubishi, Daihatsu, Isuzu, Mitsuoka, Hino, Mitsubishi Fuso, UD Trucks, Mercedes-Benz, BMW, Audi, Volkswagen, Porsche, Mini, Volvo, Peugeot, Renault, Citroen, Fiat, Alfa Romeo, Abarth, Jeep, Chevrolet, Ford, Cadillac, Dodge, Chrysler, Tesla, Jaguar, Land Rover, Rolls-Royce, Bentley, Aston Martin, McLaren, Lotus, Ferrari, Lamborghini, Maserati, Smart, Opel, DS, Alpine, Saab, BYD, Hyundai, Kia. Leave empty for all makers. Via API the Japanese name, aliases (Benz, VW) or the carsensor code (bTO) are accepted; anything else is refused with the full list.
• model (optional): client-side substring filter on the model/grade name (Japanese matches best).
• priceMin / priceMax (optional): 万円 = 10,000 JPY units (150 = ¥1,500,000). yearMin / yearMax (optional): first-registration year.
• detailFetch (default false) / maxItems (default 10, max 10000) / maxApiRequests (default 30, max 60) / proxyConfiguration (default none).

Pricing

Pay per result — see the pricing tab. A maker × prefecture query is typically hundreds to thousands of vehicles upstream; maxItems caps what you take.

FAQ

Where does the data come from? Live from carsensor.net's public, login-free static list and vehicle detail pages at run time. Every record embeds the source, source URL, a license note, and the retrieval timestamp.

Is this an official carsensor.net / Recruit service? No. Unofficial, independently built and maintained, and not affiliated with or endorsed by Recruit Co., Ltd. It reads only publicly available pages.

Are reviews or dealer marketing texts included? No. Dealer review scores/texts and reviewer names are never extracted, and neither is dealer marketing prose (sales copy, catch-phrases, photo captions) — deliberately: review prose is user-generated copyrighted content, and marketing copy stays on the source site. The output is strictly factual vehicle data plus the dealer's business identity (name/address — business information, not personal data). Phone numbers are never collected.

Who is responsible for how the data is used? You are. The Actor collects publicly available factual data politely, but the legality of your specific use (redistribution, database rights, the source site's terms) is your responsibility as the user.

Are prices accurate? Prices are what carsensor.net advertised at retrieval time: priceJpy is the base vehicle price, totalPaymentJpy the advertised total payment including fees. They change constantly — treat them as a snapshot, and re-run for fresh data.

What about server load? Strictly serial requests, ≥1.2 s apart, ~30 vehicles per list page, one extra request per vehicle detail (opt-in), hard per-run request budget (max 60), exponential backoff, no CAPTCHA/login/block evasion. If carsensor.net changes its page format or refuses a request mid-crawl (403/429/5xx), the Actor stops instead of silently mis-parsing. A stop that happens after some records were already collected ends the run successfully with complete: false and a stopReason in RUN_SUMMARY, and you are billed only for the records actually delivered; a stop before the first record fails the run visibly.

Search terms this Actor answers

carsensor scraper · carsensor.net scraper · Japan used car export data · Japan used car scraper · JDM cars database · Japanese used car prices · Japan used car auction alternative · used car Japan dataset · 中古車 データ · Japan car dealer listings · JDM import sourcing · Japanese domestic market cars · used hybrid Japan · kei truck export

More Japan data Actors by the same developer

• Japan Hotels & Ryokan Prices — hotel/ryokan prices and facility facts from jalan.net.
• Japan Government Tenders & Awards — tender notices and award results from the kkj.go.jp portal.
• Japan Medical Facilities — every registered hospital, clinic, dental clinic, and pharmacy (MHLW open data).
• Japan Care Facilities — long-term care providers across 35 service types (MHLW open data, CC BY).
• Japan Government Subsidies & Grants — open subsidy calls from the official jGrants API.
• Japan Renewable Energy FIT/FIP Facilities — METI-certified renewable installations, privacy-safe schema.
• Japan Financial Licenses & Registrations — FSA-licensed banks, securities firms, crypto exchanges and more.
• Japan Construction & Real-Estate Licenses — licensed contractors and brokers from MLIT's official register.
• Japan Trade Statistics — monthly import/export flows by HS code and partner country, from Japan Customs.

---

Unofficial tool; not affiliated with Recruit Co., Ltd. Publicly available data only; users are responsible for compliance with the source site's terms and applicable law. No personal data is collected.