# Encar Used Car Collector (`skcho/encar-car-collector`) Actor

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.

- **URL**: https://apify.com/skcho/encar-car-collector.md
- **Developed by:** [seungkyu cho](https://apify.com/skcho) (community)
- **Categories:** E-commerce, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Encar Used Car Collector

Korea's largest used-car marketplace, as a structured dataset — every listing
under the manufacturer/model tree, with the history that actually decides a price.

Accident records, insurance history, inspection results, factory options, dealer
and region. The fields a buyer squints at, in columns you can query.

### What a row looks like

```json
{
  "recordType": "encarVehicle",
  "manufacturer": "BMW",
  "modelGroup": "3시리즈",
  "modelName": "320i",
  "gradeName": "M Sport",
  "yearMonth": "2021-08",
  "priceManwon": 3980,
  "originPriceManwon": 6120,
  "mileage": 41200,
  "fuelName": "가솔린",
  "transmissionName": "오토",
  "colorName": "화이트",
  "region": "경기",
  "sellStatus": "판매중",
  "optionsStandard": ["헤드업디스플레이", "어라운드뷰"],
  "record": { "accidentCount": 0, "ownerChanges": 1, "repairedParts": [] },
  "photoUrls": ["https://ci.encar.com/..."],
  "detailUrl": "https://fem.encar.com/cars/detail/40852960",
  "scrapedAt": "2026-08-26T04:33:18.550Z"
}
```

Prices are in **만원 (10,000 KRW)** exactly as Encar quotes them — no lossy
conversion.

### How it finds listings

Encar's search is a faceted tree, not a flat list. This actor walks
**manufacturer → model group → model**, and reuses the query string the API
itself returns for each facet rather than reconstructing Encar's bespoke query
grammar. That is why stacked filters compose correctly instead of silently
dropping.

Three stages: build the taxonomy, list each group, then fetch detail per vehicle.

### Input

```json
{
  "carType": "for",
  "manufacturers": ["BMW"],
  "modelGroups": ["3시리즈"],
  "taxonomyDepth": "model",
  "yearRange": [2020, null],
  "priceRange": [null, 4000],
  "accidentTypes": ["N"],
  "sortBy": "PriceAsc",
  "maxListingsPerGroup": 20,
  "maxTotalListings": 200,
  "collectDetail": true,
  "collectRecord": true,
  "collectInspection": true
}
```

28 filters are available — fuel, transmission, body type, seats, colour, region,
service history, seller type, options and more. Leave them empty to sweep broadly,
or stack them to carve out exactly one segment.

| Field | Meaning |
|---|---|
| `carType` | `for` (imported) or `kor` (domestic) |
| `taxonomyDepth` | `modelGroup` for breadth, `model` for precision |
| `collectRecord` / `collectInspection` / `collectDiagnosis` | The history data — an extra request each |
| `maxListingsPerGroup` / `maxTotalListings` | Budget per facet and overall |
| `proxyConfiguration` | Residential by default — required, see below |

### Two things to know before running

**A residential proxy is not optional.** Encar refuses datacenter IP addresses at
the network layer — the connection fails outright, and no amount of retrying from
a cloud server gets through. `proxyConfiguration` defaults to Apify's residential
group for exactly that reason. Residential traffic is billed by Apify on top of
compute.

**The same car gets listed twice.** Dealers re-post vehicles under new ad IDs, so
de-duplicating on the ad ID alone leaves the same physical car in your results
more than once — in a 200-row sample, 21% were repeats. Rows are de-duplicated on
`vehicleId` instead, which means **a run can return fewer rows than you asked
for**: request 200 and you may get 144 unique cars. You are billed for what you
receive. Set `allowDuplicateVehicles: true` if you are tracking listings rather
than vehicles.

### Good for

- Price modelling against mileage, year and accident history
- Dealer inventory and regional supply analysis
- Spotting underpriced listings in a segment
- Tracking how long specific models sit on the market

### Notes

- Taxonomy rows go to a separate `encar-taxonomy` dataset so they do not count as
  results. `taxonomyToDefaultDataset: true` restores the old mixed shape.
- `writeMarkdown` emits a readable per-vehicle summary file alongside the dataset.

# Actor input Schema

## `carType` (type: `string`):

Which Encar tab to walk: imported (수입), domestic (국산) or both.

## `manufacturers` (type: `array`):

Limit to these manufacturers. Leave empty for all.

## `modelGroups` (type: `array`):

Limit to these model groups. Options appear once a manufacturer is picked.

## `taxonomyDepth` (type: `string`):

How deep to split the taxonomy before listing ads.

## `yearRange` (type: `array`):

Model year range. Leave a side empty for open-ended.

## `priceRange` (type: `array`):

Asking price in 만원. Leave a side empty for open-ended.

## `mileageRange` (type: `array`):

Odometer range in km. Leave a side empty for open-ended.

## `fuelTypes` (type: `array`):

Fuel

## `transmissions` (type: `array`):

Transmission

## `categories` (type: `array`):

Body Category

## `seatingCapacities` (type: `array`):

Seating Capacity

## `colors` (type: `array`):

Color

## `accidentTypes` (type: `array`):

Accident History

## `conditions` (type: `array`):

Published Records

## `services` (type: `array`):

Encar Services

## `sellTypes` (type: `array`):

Sale Type

## `regions` (type: `array`):

Region

## `options` (type: `array`):

All selected options must be present (AND), same as Encar's own filter.

## `sortBy` (type: `string`):

Listing order within each taxonomy group.

## `maxListingsPerGroup` (type: `integer`):

Maximum ads to take from each taxonomy group. 0 = all.

## `maxTotalListings` (type: `integer`):

Hard cap on ads collected across the whole run. 0 = unlimited.

## `collectDetail` (type: `boolean`):

Fetch each ad's detail page data (spec, options, description, photos). Off = list rows only, much faster.

## `collectRecord` (type: `boolean`):

Also fetch the published 보험이력 (accident counts and per-claim repair costs, owner changes, total loss).

## `collectInspection` (type: `boolean`):

Also fetch the 성능·상태 점검기록부: accident/simple-repair flags and the per-panel 교환·판금 breakdown.

## `collectDiagnosis` (type: `boolean`):

Also fetch the 엔카진단 report per vehicle where one exists.

## `writeMarkdown` (type: `boolean`):

Write one Markdown file per vehicle in addition to the dataset rows.

## `concurrency` (type: `integer`):

How many vehicles to fetch detail for at once (1-8).

## `requestDelayMs` (type: `integer`):

Pause between API requests inside each worker.

## `taxonomyToDefaultDataset` (type: `boolean`):

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.

## `proxyConfiguration` (type: `object`):

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.

## `allowDuplicateVehicles` (type: `boolean`):

Off by default: when the same car appears under more than one ad id, only the first is kept. Leaving duplicates in inflated a 200-row result by about 21%. Turn on if you are tracking listings rather than vehicles.

## Actor input object example

```json
{
  "carType": "for",
  "manufacturers": [],
  "modelGroups": [],
  "taxonomyDepth": "modelGroup",
  "fuelTypes": [],
  "transmissions": [],
  "categories": [],
  "seatingCapacities": [],
  "colors": [],
  "accidentTypes": [],
  "conditions": [],
  "services": [],
  "sellTypes": [],
  "regions": [],
  "options": [],
  "sortBy": "ModifiedDate",
  "maxListingsPerGroup": 20,
  "maxTotalListings": 200,
  "collectDetail": true,
  "collectRecord": true,
  "collectInspection": true,
  "collectDiagnosis": false,
  "writeMarkdown": true,
  "concurrency": 4,
  "requestDelayMs": 300,
  "taxonomyToDefaultDataset": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "allowDuplicateVehicles": false
}
```

# Actor output Schema

## `results` (type: `string`):

One row per unique vehicle with price, mileage, options and accident/inspection history.

## `taxonomy` (type: `string`):

The facet tree the crawl walked, with listing counts per group. Kept out of the main dataset so it does not count as results.

## `files` (type: `string`):

A readable per-vehicle summary plus the taxonomy overview.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("skcho/encar-car-collector").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("skcho/encar-car-collector").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call skcho/encar-car-collector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,skcho/encar-car-collector"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/8FfMUTq6LmajWNHeJ/builds/Oop8H2KFnldHrhdW6/openapi.json