/daangn/jobs

POST /api/daangn/jobs

Price: 1 credit

Get a Daangn (당근) part-time job post by id or URL: title, description, employer, pay, pay basis and pay method, work days, dates and hours, applicant requirements, job tasks, workplace address and coordinates, view and application counts, and the employer's hire count, response rate and review summary

How to use it

Job ids come from daangn/jobs/search. Pay is in KRW per the salary_type basis. work_dates holds the calendar days of a short-term job.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Daangn part-time job post id or URL (examples: "7ht6ynhmmd9i", "https://jobs.daangn.com/job-posts/7ht6ynhmmd9i"; minLength: 1)

Response

• @type string (default: "DaangnJob")
• id string required
• url string required
• description string nullable
• company_name string nullable
• business_type string nullable
• employment_type string nullable
• status string nullable
• is_closed boolean nullable
• salary number nullable
• salary_type string nullable
• salary_pay_method string nullable
• job_tasks array (default: [])
• job_task_meta object (default: {})
  • * object
    • * union
• application_requirements array (default: [])
• considered_qualifications array (default: [])
• onboarding_periods array (default: [])
• event_names array (default: [])
• work_dates array (default: [])
• work_days array (default: [])
• work_start string nullable
• work_end string nullable
• work_period string nullable
• is_work_time_negotiable boolean nullable
• is_work_days_negotiable boolean nullable
• welfare array (default: [])
• workplace_address string nullable
• workplace_road_address string nullable
• latitude number nullable
• longitude number nullable
• region_id string nullable
• city string nullable
• district string nullable
• neighborhood string nullable
• images array (default: [])
• accepts_phone_contact boolean nullable
• has_business_license boolean nullable
• employer object nullable
  • @type string (default: "DaangnEmployer")
  • id string nullable
  • nickname string nullable
  • image string nullable
  • region string nullable
  • manner_temperature number nullable
  • hire_count integer nullable
  • response_rate number nullable
  • review_count integer nullable
  • great_review_count integer nullable
  • good_review_count integer nullable
  • bad_review_count integer nullable
  • review_highlights object (default: {})
    • * integer
  • is_identity_verified boolean nullable
  • is_perfect_author boolean nullable
  • last_active_at integer nullable
• view_count integer nullable
• watch_count integer nullable
• application_count integer nullable
• created_at integer nullable
• published_at integer nullable
• closed_at integer nullable
• bumped_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 job post 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.