/jobkorea/jobs

POST /api/jobkorea/jobs

Price: 10 credits

Get one JobKorea (jobkorea.co.kr) job posting by id or URL: title, status, the full posting text and images, posting and application dates, work fields, employment type, experience and education requirements, pay, schedule, workplaces with coordinates, application methods and the hiring company

How to use it

Pass an id from jobkorea/jobs/search, not its legacy_id. Headhunting postings come back with the title, summary, keywords and text only. pay_min and pay_max are KRW per pay_type.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — JobKorea job posting id or URL (examples: "50090009", "https://www.jobkorea.co.kr/Recruit/GI_Read/50090009"; minLength: 1)

Response

• @type string (default: "JobkoreaJob")
• id string required
• url string required
• legacy_id string nullable
• status string nullable
• posting_type string nullable
• is_headhunting boolean nullable
• summary string nullable
• text string nullable
• images array (default: [])
• posted_at integer nullable
• first_posted_at integer nullable
• updated_at integer nullable
• application_start_at integer nullable
• application_end_at integer nullable
• is_always_hiring boolean nullable
• closes_on_hire boolean nullable
• work_fields array (default: [])
• keywords array (default: [])
• vacancy_count integer nullable
• employment_types array (default: [])
• employment_type string nullable
• experience string nullable
• experience_min_years integer nullable
• experience_max_years integer nullable
• education string nullable
• graduation_status string nullable
• gender string nullable
• pay_type string nullable
• pay_min number nullable
• pay_max number nullable
• work_week_type string nullable
• work_hours string nullable
• workplaces array (default: [])
  • @type string (default: "JobkoreaWorkplace")
  • address string nullable
  • latitude number nullable
  • longitude number nullable
• application_methods array (default: [])
• apply_url string nullable
• hr_manager_name string nullable
• hr_manager_department string nullable
• company object nullable
  • @type string (default: "JobkoreaJobCompany")
  • id string nullable
  • url string nullable
  • name string nullable
  • company_type string nullable
  • business_number string nullable
  • industry string nullable
  • listing_status string nullable
  • employee_count integer nullable
  • address string nullable
  • latitude number nullable
  • longitude number nullable
  • open_job_count 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 — JobKorea has no job posting 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.