CarSensor Japan Scraper - Used Cars, Prices & Dealers
Pricing
from $1.60 / 1,000 car results
CarSensor Japan Scraper - Used Cars, Prices & Dealers
Scrape CarSensor (carsensor.net) used car listings across Japan by maker, model, prefecture, filters or URL. Extract prices, year, mileage, inspection, warranty, equipment, quality reports, photos and dealer details. Supports recurring price change monitoring.
Pricing
from $1.60 / 1,000 car results
Rating
0.0
(0)
Developer
Abot API
Maintained by CommunityActor stats
1
Bookmarked
1
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Features
Share
CarSensor Scraper: Japan Used Car Listings, Prices, Specs and Dealers
Collect used car listings from CarSensor (carsensor.net), Japan's largest used car marketplace: total and base price, model year, mileage, vehicle inspection, repair history, warranty, the full equipment list, the quality report, every photo and the selling dealer with address, hours and phone. Search by maker, model, prefecture and filters, or paste result pages, dealer pages and single car pages, and monitor price changes on a schedule.
Why This Scraper?
- Two ways in. Search by maker, model, prefecture, body type, keyword, price, model year range and mileage, or paste any result page, dealer page or single car page.
- Complete cars. Each record carries price, year, mileage, inspection, repair history, warranty, drive, transmission, seats, doors, fuel, colour and body type, plus the equipment that is actually fitted, the sample loan example and the model's catalogue specs (dimensions, weight, fuel economy).
- Quality and photos. The quality score, the inspector's comment, the inspection date and every photo of the car, plus the 360 view id when the listing has one.
- Dealer block. Dealer name, page, address, opening hours, phone, catch copy, review score and count, plus the dealer's coupons and current fair on every car.
- Price monitoring. Recurring updates label each car NEW, UPDATED, UNCHANGED, REAPPEARED or EXPIRED, and a price-only mode returns just the cars whose price moved.
- Resume and export. Continue an interrupted run, and pipe results into Notion, Linear or Airtable.
- Transparent billing. One charge per car, plus one detail charge for each car whose own page was read.
Use Cases
- Dealers and traders: benchmark your stock against live market prices by maker, model, year and mileage.
- Market analysts: track asking prices, mileage and equipment trends for a model across prefectures.
- Exporters and buyers: build shortlists with photos, quality scores, repair history and dealer contacts.
- Price alerts: run a schedule with price-only recurring updates and receive just the cars that got cheaper.
- Data teams: feed a clean, flat car dataset into a warehouse or a model.
Data You Get
Sample shape: values are illustrative placeholders, not from a live record.
| Field | Example |
|---|---|
carId | AU0000000000 |
detailUrl | https://www.carsensor.net/usedcar/detail/AU0000000000/index.html |
maker, model, grade | Example Maker, Example Model, 2.0 Example Grade 4WD |
totalPriceManYen, basePriceManYen | 250.5, 239.8 (10,000 yen) |
totalPriceJpy, basePriceJpy | 2505000, 2398000 |
year, yearJp, mileageKm, mileageText | 2021, R03, 32000, 3.2δΈkm |
inspection, repairHistory | 2027(R09)εΉ΄6ζ, γͺγ |
warranty, warrantyDetail, legalMaintenanceDetail | δΏθ¨Όδ», full warranty text, full maintenance text |
monthlyLoanJpy, loan | 73800, object with loanType, monthlyPaymentJpy, annualRatePercent, firstPaymentJpy, downPaymentJpy, installments, bonusAddition, totalInstallmentPriceJpy |
catalogSpecs | object with releaseDate, dimensions, lengthMm, widthMm, heightMm, wheelbase, weight, interiorDimensions, fuelEconomyWltc, minTurningRadius |
displacementCc, transmission, drive, steering | 1986, γγγ’CVT, 4WD, ε³ |
seats, doors, fuel, engineType, bodyType, color | 5, 5, γ¬γ½γͺγ³, γ¬γ½γͺγ³, γγγγ³, η½ |
equipment | ["ETC", "γΉγγΌγγγΌ", "γγ©γ€γγ¬γ³γΌγγΌ"] |
qualityScore, qualityComment, qualityInspectionDate | 4.5, inspector comment, 2026-10-31 |
labels | ["360Β°η»εδ»", "θ»δΈ‘εθ³ͺθ©δΎ‘ζΈδ»"] |
mainImageUrl, imageUrls, imageCount, view360CarId | first photo, all photos, 60, U00000000000 |
prefecture, city, region | ζ±δΊ¬ι½, Example City, ι’ζ± |
makerCode, makerEn, prefectureCode, prefectureEn | TO, Toyota, 35, Tokyo |
shopId, shopName, shopUrl, shopCatch | 000000000, Example Motors, dealer page, catch copy |
shopAddress, shopHours, shopPhone, shopPhoneNote | address, 10:00ο½18:30, 0078-0000-000000, dial note |
shopCoupons, shopOffer, shopImageUrl | list of type, title, validity; fair headline; banner image |
shopReviewScore, shopReviewCount, detailError | 4.5, 100, set only when a car's own page could not be read |
searchUrl, page, scrapedAt | result page link, 1, timestamp |
Recurring-update rows add changeType, changedFields, firstSeenAt and lastSeenAt.
How to Use
- Pick a mode: Search by filters or Paste links.
- Set the filters (maker, model, prefecture, body type, keyword, price, model year range, mileage, sort) or paste your links.
- Set Max items (default 20) and leave Read each car's own page on for the full record.
- Run the actor and download the dataset as JSON, CSV or Excel.
Search a model in one prefecture:
{"mode": "search","maker": "Toyota","model": "S149","prefecture": "chiba","maxItems": 50}
Search by keyword with filters:
{"mode": "search","keywords": "γγͺγ¦γΉ","minPrice": 1000000,"maxPrice": 2000000,"minYear": 2018,"maxYear": 2023,"bodyType": "suv","maxMileageKm": 50000,"sortBy": "totalPriceAsc","maxItems": 100}
Paste links:
{"mode": "url","urls": ["https://www.carsensor.net/usedcar/bTO/s149/index.html","https://www.carsensor.net/usedcar/detail/AU0000000000/index.html","https://www.carsensor.net/shop/chiba/000000000/"],"maxItems": 100}
Supported links
Result pages for the whole country, a maker, a maker and model, a maker, model and prefecture, a body-type page and a search with filters; a maker index page (read as the maker's result list); links with a sort parameter or a later page number; the site address with or without www; single car pages (detail and lease pages, tracking parameters are fine); and dealer pages, whose full stock list is read. Links copied from page source with & work too. Pages that are not cars (help, home, other sites) are refused with a message. Pagination starts at the page named in the link and walks forward.
Run it from your code
Python:
from apify_client import ApifyClientclient = ApifyClient("<YOUR_APIFY_TOKEN>")run = client.actor("<ACTOR_ID>").call(run_input={"mode": "search","maker": "Toyota","maxItems": 20,})for car in client.dataset(run["defaultDatasetId"]).iterate_items():print(car["fullTitle"], car["totalPriceManYen"], car["mileageKm"])
JavaScript:
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });const run = await client.actor('<ACTOR_ID>').call({ mode: 'search', maker: 'Toyota', maxItems: 20 });const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items.length);
Tips
- Finding a model code: open the model's result page on the site; the code is the part after the s in the address, for example S149 in /usedcar/bTO/s149/.
- Keyword with a maker: the keyword narrows inside the maker, model and prefecture you set.
- Max items versus max pages: Max items is the single limit that stops a run. Max pages is an optional guard per search or link and never caps the run on its own.
- Dealer pages: a pasted dealer page returns that dealer's whole stock, read from each car's own page, so every row carries the detail charge.
Resume and recurring updates
Continue a previous run finishes ONE interrupted run: give its run id and every car it already collected is skipped. Recurring updates is for running the same search on a schedule: each run returns what changed since the last one. Both together are refused once a baseline exists. A run that stopped early, or that started from a pasted page beyond the first, never reports cars as gone.
Dataset views
Results (headline fields), Car details (spec table, equipment, quality report, photos), Dealers, and Changes (recurring-update rows).
Send results into your apps (MCP connectors)
Optionally pipe the scraped cars into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step after the scrape: the Apify dataset is never changed.
What gets written to the connector: a condensed, human-readable summary of each car, not the full JSON. Each car becomes one entry with a title and its key fields flattened to plain text. The complete record always stays in the Apify dataset.
- Authorize a connector once under Apify > Settings > Integrations (Notion, Linear, Airtable, or Apify).
- Select it in the "Pipe results into your apps" input field. (If the picker is empty, you haven't authorized a connector yet.)
- For Notion, also set
notionParentPageUrlto the page where cars should be created.
The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.
Input Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
mode | string | search | search filters or url pasted links. |
keywords | string | none | Free-text search, for example a model name. |
maker | string | none | Maker code (TO), Japanese name or common English name. |
model | string | none | Model code from the site's address, for example S149. Needs a maker. |
prefecture | string | any | One of the 47 prefectures. |
minPrice | integer | none | Lowest total price in yen. |
maxPrice | integer | none | Highest total price in yen. |
minYear | integer | none | Earliest model year. |
maxYear | integer | none | Latest model year. |
bodyType | string | any | Coupe, minivan, hatchback, wagon, convertible, SUV, pickup, sedan, truck or other. |
maxMileageKm | integer | none | Highest mileage in km. |
sortBy | string | default | Site default, newest, price ascending or descending, newest year, lowest mileage. |
urls | array | sample links | Result pages, dealer pages and single car pages. |
fetchDetails | boolean | true | Read each car's own page for the full record. |
maxPages | integer | none | Optional guard per search or link; empty means no page limit. |
maxItems | integer | 20 | The single limit that stops a run; 0 means no limit. |
proxy | object | standard Apify proxy | Proxy settings. |
resumeFromRunId | string | none | Run id of an interrupted run to continue. |
incrementalMode | boolean | false | Label cars against the previous run of the same setup. |
stateKey | string | none | Name the baseline of a recurring schedule. |
emitUnchanged | boolean | false | Also return unchanged cars. |
emitExpired | boolean | false | Also return cars that are gone. |
changeScope | string | all | Any listing field, or price only. |
compactUpdates | boolean | false | Short rows for updated and gone cars. |
expireAfterMissedScans | integer | 1 | Complete scans a car must be missing before it is marked gone. |
ignoreFieldsForChanges | array | none | Fields that never make a car UPDATED. |
mcpConnectors | array | none | Connectors to pipe results into after the run. |
notionParentPageUrl | string | none | Notion parent page for the Notion connector. |
maxNotifyListings | integer | 50 | Rows each connector receives per run. |
Output Example
Sample shape: values are illustrative placeholders, not from a live record.
{"carId": "AU0000000000","detailUrl": "https://www.carsensor.net/usedcar/detail/AU0000000000/index.html","maker": "Example Maker","model": "Example Model","grade": "2.0 Example Grade 4WD","fullTitle": "Example Maker Example Model 2.0 Example Grade 4WD","totalPriceManYen": 250.5,"basePriceManYen": 239.8,"totalPriceJpy": 2505000,"year": 2021,"mileageKm": 32000,"inspection": "2027(R09)εΉ΄6ζ","repairHistory": "γͺγ","warranty": "δΏθ¨Όδ»","displacementCc": 1986,"transmission": "γγγ’CVT","drive": "4WD","seats": 5,"equipment": ["ETC", "γΉγγΌγγγΌ"],"qualityScore": 4.5,"labels": ["360Β°η»εδ»"],"mainImageUrl": "https://example.com/photo.jpg","prefecture": "ζ±δΊ¬ι½","shopName": "Example Motors","shopAddress": "Example address","shopPhone": "0078-0000-000000","shopReviewScore": 4.5,"shopReviewCount": 100,"page": 1,"scrapedAt": "2026-01-01T00:00:00Z"}
Plan Requirement
The default proxy setting is the standard Apify proxy pool. In our checks the site served its pages through that pool without any special setup, so a standard run needs no action. The standard pool works on every plan; Residential is recommended for the most reliable results on large or frequent runs. If you select Residential, the run still tries the cheaper standard pool first and moves to Residential only if the site refuses it.
What the run does, in order:
- It starts on the standard Apify proxy pool.
- If that pool is refused for your account, or keeps failing, it tries Apify Residential, which only paid Apify plans include. Residential traffic from this automatic step is billed to your own Apify plan, and the run limits how much it uses. Apify free plans do not include residential proxies, and then the log prints "The selected connection is unavailable to this run" with a pointer to https://apify.com/pricing.
- It then continues on a backup connection, and the log says "Served over the backup connection" once that connection serves a page. On a free plan some pages may still be unavailable.
- If every connection is refused, the run stops as failed with "The proxy connection was refused for this account, so no page could be read" (a paid Apify plan is required) instead of returning an empty dataset. If only the backup connection was left and it could not load the pages, the message reads "No results: residential proxies are unavailable on this run".
- A page that is refused by the site, or cannot be read within the per-page time limit (about 25 seconds), skips that source with a notice in the log, and the run keeps the other sources. If no results page loaded at all, the run ends with "Could not load any results page ... This is a connection problem, not an empty search".
If you hit these messages, switch to a paid Apify plan, or supply your own proxy URLs in the proxy field (a single custom proxy is used as is, with no backup connection). For very large runs Residential is the most reliable choice.
Billing for each event is in the FAQ below, and the Pricing tab shows the current rates.
FAQ
How much does it cost?
The run is billed on three events, and the Pricing tab shows the current rate of each:
- Car result: once for every record written to the dataset, including a short
UPDATEDrow. - Detail enrichment: once for every car whose own page was read and merged into a record you receive, whether you left car page reading on, pasted a car link or pasted a dealer page. A car that is not written (an unchanged one in recurring updates) is not charged this event, and neither is a short
UPDATEDrow (compactUpdates), which carries no detail fields. - Actor Start: once per GB of memory when the run starts, at least one.
Use Max items to cap the cost of any run.
Is it legal to scrape CarSensor?
This actor collects only publicly available listing data. You are responsible for how you use it: follow the site's terms and the laws that apply to you, and get legal advice if you plan commercial redistribution. Listing photos and dealer copy may carry their own rights separate from the underlying facts.
Can I get only new or changed cars on a schedule?
Yes. Schedule the actor from the Schedules tab and turn on recurring updates. Each run then returns only new and updated cars, unchanged ones are not billed, and gone cars can be reported too once a run has scanned its scope end to end. Choose Price only to be told just about price moves.
Why were no gone cars reported this run?
Gone cars are only reported after a run that read every one of its sources to the end. If a limit stopped the run, a source hit Max pages or ran out of Max items partway through, a source failed, a pasted page started beyond the first, or the run continued a previous one, detection is skipped for the whole run (the run log says why) and the cars stay tracked. The next complete run reports them.
Why are the equipment list, photos or dealer address empty?
Those fields come from a car's own page. Leave Read each car's own page on, or paste car links directly; they are always read in full. The result page alone carries price, year, mileage, inspection, warranty, area and the dealer name.
Why did my run fail instead of returning an empty dataset?
If every page the run tried was refused, the run stops with a clear message so "no cars for this search" is never confused with "nothing could be read". Run it again in a few minutes. If only some links failed, you still get what was found, with a notice.
Can I use it with AI agents or MCP?
Yes. Call it from any Apify integration or MCP client, and use the connector field to push results into Notion, Linear or Airtable.
π Want more car data?
Pair this actor with these related scrapers from the same team:
| π mobile.de Scraper Scrape mobile.de vehicle listings with 30+ fields including price, mileage, registration... | π Auto.ru Scraper Scrape Auto.ru car listings: search by make, model, year, price, mileage, body, engine... |
| π Cars.com Scraper Scrape cars.com listings by make, ZIP and radius. 90+ fields per car: price, MSRP... | π Autotrader US Scrape US car listings from Autotrader by make, model, ZIP, price, year, body style... |
| π AutoScout24 Scraper A lean, production-grade scraper for autoscout24.com. Point it at a search, get back... | π AutoTrader UK Scraper Pull structured vehicle listings from autotrader.co.uk at scale. Search by filters or use... |
π Browse all abotapi scrapers
π¬ Support
- π Found a bug or a missing field? Open a ticket on the Issues tab. We usually reply within hours.
- π οΈ Need another site, extra fields or a private build? Email contact@abotapi.com.
- β Enjoying it? A quick review on the actor page helps other users find it.