/wanted/companies

POST /api/wanted/companies

Price: 5 credits

Get one Wanted (wanted.co.kr) company by id or URL: name, description, industry, corporation type and class, CEO, address with coordinates, website, logo and photos, founding year, size and perk tags, application response rate, headcount, average salary and sales with their industry percentile, and every open job

How to use it

Pass an id from wanted/companies/search or a job's company. wanted/companies/statistics adds salary, headcount and financial history.

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "WantedCompany")
• id string required
• url string required
• name string nullable
• insight_id string nullable
• description string nullable
• industry string nullable
• industry_detail string nullable
• corporation_type string nullable
• corporation_class string nullable
• industry_class string nullable
• ceo string nullable
• location string 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
• website_url string nullable
• homepage string nullable
• image string nullable
• images array (default: [])
• banner string nullable
• founded_year integer nullable
• business_status string nullable
• is_verified boolean nullable
• size_tags array (default: [])
  • @type string (default: "WantedTag")
  • id string nullable
  • name string nullable
  • category_id string nullable
• tags array (default: [])
  • @type string (default: "WantedTag")
  • id string nullable
  • name string nullable
  • category_id string 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
• open_position_count integer nullable
• employee_count integer nullable
• insured_employee_count integer nullable
• average_salary object nullable
  • @type string (default: "WantedCompanyMetric")
  • value number nullable
  • source string nullable
  • industry_percentile number nullable
  • updated_at integer nullable
• headcount object nullable
  • @type string (default: "WantedCompanyMetric")
  • value number nullable
  • source string nullable
  • industry_percentile number nullable
  • updated_at integer nullable
• sales object nullable
  • @type string (default: "WantedCompanyMetric")
  • value number nullable
  • source string nullable
  • industry_percentile number nullable
  • updated_at integer nullable
• jobs array (default: [])
  • @type string (default: "WantedCompanyJob")
  • id string required
  • url string required
  • status string nullable
  • due_at integer nullable
  • location string nullable
  • district string nullable
  • address string nullable
  • job_category_ids array (default: [])
  • job_group_ids array (default: [])
  • experience_min_years integer nullable
  • experience_max_years integer nullable
  • employment_type string nullable
  • additional_apply_types array (default: [])

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 company 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.