/wanted/jobs/search

POST /api/wanted/jobs/search

Price: 5 credits

Search Wanted (wanted.co.kr) job postings by keyword, or browse them by job group and category, region, experience range, employment type, applicant group, preferred language and perk tags: id, title, company with response rate, location, job group and category ids, experience range, employment type and referral reward

How to use it

With a keyword only country, regions, experience and sort apply; the other filters browse without one. Pass a returned id to wanted/jobs for the full posting.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Search keyword (examples: "python", "백엔드"; minLength: 1; maxLength: 100)
• count integer required — Max number of results (min: 1; max: 5000)
• sort string — Result ordering (default: "latest"; one of: "recommended", "latest", "popular", "response_rate")
• country string nullable — Country of the workplace (one of: "kr", "jp")
• regions array nullable — South Korean regions of the workplace (one of: "seoul", "busan", "daegu", "incheon", "gwangju", "daejeon", "ulsan", "sejong", "gyeonggi", "gangwon", "north_chungcheong", "south_chungcheong", "north_jeolla", "south_jeolla", "north_gyeongsang", "south_gyeongsang", "jeju")
• experience_min_years integer nullable — Lower bound of required experience, in years (min: 0; max: 10)
• experience_max_years integer nullable — Upper bound of required experience, in years (min: 0; max: 10)
• job_group string nullable — Job group (one of: "development", "business", "marketing", "design", "customer_service_retail", "sales", "media", "engineering", "manufacturing", "finance", "hr", "information_security", "construction", "game_production", "logistics_trade", "food_beverage", "legal", "education", "medical_pharma_bio", "public_welfare")
• job_category_ids array nullable — Wanted job category ids within the job group (examples: ["872","669"])
• employment_types array nullable — Employment types (one of: "regular", "contract", "intern")
• applicant_types array nullable — Postings open to these applicant groups (one of: "alternative_military", "foreigner", "disabled_person")
• preferred_languages array nullable — Preferred languages (one of: "en", "ja", "zh", "etc")
• attraction_tag_ids array nullable — Wanted company perk tag ids (examples: ["10597"])

Response

• @type string (default: "WantedJobSearchResult")
• id string required
• url string required
• 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
• image string nullable
• country string nullable
• location string nullable
• district string nullable
• job_group_id string nullable
• job_category_id string nullable
• 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: [])
• attraction_tag_ids array (default: [])
• skill_tag_ids array (default: [])
• reward object nullable
  • @type string (default: "WantedReward")
  • total string nullable
  • referrer_amount number nullable
  • applicant_amount number nullable
  • currency string nullable
• is_outlink boolean 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 — 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.