Encar Used Car Collector
Pricing
from $2.00 / 1,000 results
Crawl the Encar (encar.com) manufacturer/model taxonomy to enumerate used car listings, then collect per-listing detail including accident records, inspection and diagnosis data.
Pricing
from $2.00 / 1,000 results
Rating
0.0
(0)
Developer
seungkyu cho
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
15 hours ago
Last modified
Categories
Share
Which Encar tab to walk: imported (수입), domestic (국산) or both.
Limit to these manufacturers. Leave empty for all.
[]Limit to these model groups. Options appear once a manufacturer is picked.
[]How deep to split the taxonomy before listing ads.
All selected options must be present (AND), same as Encar's own filter.
[]Listing order within each taxonomy group.
Maximum ads to take from each taxonomy group. 0 = all.
Hard cap on ads collected across the whole run. 0 = unlimited.
Fetch each ad's detail page data (spec, options, description, photos). Off = list rows only, much faster.
Also fetch the published 보험이력 (accident counts and per-claim repair costs, owner changes, total loss).
Also fetch the 성능·상태 점검기록부: accident/simple-repair flags and the per-panel 교환·판금 breakdown.
Also fetch the 엔카진단 report per vehicle where one exists.
Write one Markdown file per vehicle in addition to the dataset rows.
How many vehicles to fetch detail for at once (1-8).
Pause between API requests inside each worker.
Off by default: manufacturer/model taxonomy rows go to a separate "encar-taxonomy" dataset so they do not count as results. Turn on only if a downstream consumer expects taxonomy and vehicle rows mixed in one dataset.
Encar blocks datacenter IP addresses outright, so a run without a residential proxy cannot reach the API from the Apify platform. Residential proxy traffic is billed separately by Apify.
{ "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ]}