/daangn/cars

POST /api/daangn/cars

Price: 1 credit

Get a Daangn (당근) used-car listing by id or URL: model, body type, year, mileage, engine, transmission, price or monthly lease fee, accident and owner-change history, options, photos, location and the seller

How to use it

Car ids come from daangn/cars/search. Money is in KRW.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• car string required — Daangn used-car listing id or URL (examples: "p86t4iqn33cj", "https://www.daangn.com/kr/cars/그랜저hg-p86t4iqn33cj/"; minLength: 1)

Response

• @type string (default: "DaangnCar")
• id string required
• numeric_id string nullable
• url string required
• description string nullable
• deal_type string nullable
• status string nullable
• price number nullable
• lease_monthly_fee number nullable
• lease_acquisition_price number nullable
• lease_deposit number nullable
• lease_residual_value number nullable
• lease_started_at integer nullable
• lease_ended_at integer nullable
• lease_end_option string nullable
• car_name string nullable
• car_type string nullable
• maker string nullable
• fuel_type string nullable
• transmission string nullable
• model_year integer nullable
• registration_year integer nullable
• registration_month integer nullable
• mileage_km integer nullable
• engine_cc integer nullable
• options array (default: [])
• own_damage_accident_count integer nullable
• total_and_flood_accident_count integer nullable
• owner_change_count integer nullable
• business_use string nullable
• images array (default: [])
• latitude number nullable
• longitude number nullable
• region object nullable
  • @type string (default: "DaangnRegion")
  • id string nullable
  • name string nullable
  • city string nullable
  • district string nullable
  • neighborhood string nullable
• seller object nullable
  • @type string (default: "DaangnUserRef")
  • id string nullable
  • numeric_id string nullable
  • url string nullable
  • nickname string nullable
  • image string nullable
  • manner_temperature number nullable
  • review_count integer nullable
  • region object nullable
    • @type string (default: "DaangnRegion")
    • id string nullable
    • name string nullable
    • city string nullable
    • district string nullable
    • neighborhood string nullable
• chat_count integer nullable
• view_count integer nullable
• favorite_count integer nullable
• published_at integer nullable

Errors

• 422 — The request body did not validate 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 — Daangn has no car listing under that id 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.