/wanted/jobs

POST /api/wanted/jobs

Price: 1 credit

Get one Wanted (wanted.co.kr) job posting by id or URL: title, status, deadline, the full posting text (intro, tasks, requirements, preferred points, benefits, hiring process), company, address with coordinates, job group and categories, skill and perk tags, experience range, employment type and referral reward

How to use it

Pass an id from wanted/jobs/search or a wanted.co.kr/wd/ link. Closed postings still answer, with status close.

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "WantedJob")
• id string required
• url string required
• status string nullable
• due_at integer nullable
• intro string nullable
• main_tasks string nullable
• requirements string nullable
• preferred_points string nullable
• benefits string nullable
• hiring_process string nullable
• employment_note string nullable
• highlight string nullable
• company object nullable
  • @type string (default: "WantedJobCompany")
  • id string nullable
  • name string nullable
  • url string nullable
  • image string nullable
  • country_code string nullable
  • open_position_count integer nullable
  • response_stats object nullable
    • @type string (default: "WantedResponseStats")
    • response_rate number nullable
    • level string nullable
    • reply_type string nullable
    • applications_count integer nullable
    • avg_response_days number nullable
• address object nullable
  • @type string (default: "WantedJobAddress")
  • country string nullable
  • country_code string nullable
  • location string nullable
  • district string nullable
  • address string nullable
  • road_address string nullable
  • latitude number nullable
  • longitude number nullable
• job_group object nullable
  • @type string (default: "WantedTag")
  • id string nullable
  • name string nullable
  • category_id string nullable
• job_categories array (default: [])
  • @type string (default: "WantedTag")
  • id string nullable
  • name string nullable
  • category_id string nullable
• skill_tags array (default: [])
  • @type string (default: "WantedTag")
  • id string nullable
  • name string nullable
  • category_id string nullable
• attraction_tags array (default: [])
  • @type string (default: "WantedTag")
  • id string nullable
  • name string nullable
  • category_id string nullable
• images array (default: [])
• experience_min_years integer nullable
• experience_max_years integer nullable
• is_newbie boolean nullable
• employment_type string nullable
• additional_apply_types array (default: [])
• preferred_languages array (default: [])
• reward object nullable
  • @type string (default: "WantedReward")
  • total string nullable
  • referrer_amount number nullable
  • applicant_amount number nullable
  • currency string nullable
• application_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 — Wanted 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.