/daangn/cars/search

POST /api/daangn/cars/search

Price: 10 credits

Search Daangn (당근) used cars for sale, lease or rental around a neighbourhood, by keyword, body type, maker, fuel, transmission, deal type, price, model year and mileage: one row per car with model, year, mileage, price or monthly fee, status, photos and posting time

How to use it

Take region_id from daangn/regions/search. Pass a returned id to daangn/cars for the history, options and seller. Money is in KRW. maker takes the Korean name (현대, 기아, ...); price_min and price_max apply to cars for sale, not to rental or lease listings.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• region_id integer required — Daangn neighbourhood (dong) id (examples: 6035; min: 1)
• keyword string nullable — Model or keyword (examples: "그랜저"; minLength: 1)
• car_types array nullable — Body types; any may match (one of: "small", "middle", "big", "suv", "business", "etc")
• maker string nullable — Maker as Daangn names it, or its numeric maker id (examples: "현대", "기아", "제네시스", "쉐보레", "벤츠", "BMW", "5"; minLength: 1)
• fuel_types array nullable — Fuel types; any may match (one of: "gasoline", "gasoline_electronic", "diesel", "diesel_electronic", "lpg_gasoline", "lpg", "lpg_electronic", "cng", "electronic", "fuel_cell_electronic", "hybrid", "h2o_electronic")
• gears array nullable — Transmissions; any may match (one of: "auto", "semi_auto", "manual", "cvt")
• sale_types array nullable — Deal types: sale, rental or lease; any may match (one of: "sale", "rental", "lease")
• price_min integer nullable — Minimum sale price, KRW; applies to cars for sale (min: 0)
• price_max integer nullable — Maximum sale price, KRW; applies to cars for sale (min: 0)
• model_year_min integer nullable — Earliest model year (min: 1900; max: 2100)
• model_year_max integer nullable — Latest model year (min: 1900; max: 2100)
• mileage_km_min integer nullable — Minimum mileage, km (min: 0)
• mileage_km_max integer nullable — Maximum mileage, km (min: 0)
• only_on_sale boolean — Exclude reserved and sold cars (default: false)
• count integer required — Max number of cars to return (min: 1; max: 300)

Response

• @type string (default: "DaangnCarCard")
• id string required
• url string required
• car_name string nullable
• car_type string nullable
• model_year integer nullable
• mileage_km integer nullable
• deal_type string nullable
• status string nullable
• price number nullable
• lease_monthly_fee number nullable
• options array (default: [])
• images array (default: [])
• region_name string nullable
• chat_count integer nullable
• view_count integer nullable
• favorite_count integer nullable
• published_at integer nullable

Errors

• 422 — Daangn has no neighbourhood under that region_id, or no car maker under that maker name Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.