Bytbil Car Listings Scraper
Pricing
Pay per event
Bytbil Car Listings Scraper
Collect structured public car listings from Bytbil search and detail pages.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Sam Towers
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Share
A platform-neutral, asynchronous scraper for public bytbil.com search and vehicle-detail pages. It follows numbered search pagination, deduplicates by listing ID, and streams normalized records rather than retaining page bodies.
Functional input
Input is JSON with startUrls (non-empty array of HTTPS Bytbil URL strings or { "url": ... } objects), optional maxItemsPerStartUrl (1–1000, default 100), optional concurrency (1–20, default 8), and optional proxyUrl. A proxy is not required.
On Apify, provide a startUrls list such as [{"url":"https://www.bytbil.com/bil"}] and optionally set maxItemsPerStartUrl, concurrency, or proxyUrl. A direct detail URL can be used when one vehicle is needed. The Actor writes records to its default dataset.
For local development, run PYTHONPATH=src python -m bytbil_scraper.cli input.json. Standard output is JSON Lines records; standard error contains platform-neutral billable-event signals.
Output
Each record contains listingId, title, url, numeric price, displayedPrice, modelYear, mileageMil, fuelType, location, and sourceSearchUrl. A field is null when the public listing does not provide it.
The scraper emits one result-item event only after the corresponding persistence callback succeeds. The deployment adapter owns the memory-scaled apify-actor-start event because allocated memory is an Apify runtime fact.
The Actor charges one result-item event for each listing successfully stored in the default dataset and one memory-scaled Actor-start event per run, with a minimum of one start event. It uses direct public HTTP requests by default; public-site changes, unavailable pages, rate limits, and proxy or network failures can limit results.
