/wanted/companies/statistics

POST /api/wanted/companies/statistics

Price: 5 credits

Get the Wanted (wanted.co.kr) statistics of one company by id or URL: average and new-hire salary by data source with industry and overall averages, monthly salary history, salary by education and position level, headcount with monthly hires and departures, average years of service, sales and yearly financial results

How to use it

Takes a company id or the insight_id from wanted/companies/search. Salaries and sales are in KRW.

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, URL or insight id (examples: "24000", "https://www.wanted.co.kr/company/24000", "42abb65f9f82db2de08ad6807a422cdc552ffa20"; minLength: 1)

Response

• @type string (default: "WantedCompanyStatistics")
• company_id string nullable
• url string nullable
• name string nullable
• insight_id string nullable
• average_salaries array (default: [])
  • @type string (default: "WantedSalaryFigure")
  • source string nullable
  • salary number nullable
  • industry_percentile number nullable
  • industry_average number nullable
  • overall_average number nullable
  • updated_at integer nullable
• new_hire_salaries array (default: [])
  • @type string (default: "WantedSalaryFigure")
  • source string nullable
  • salary number nullable
  • industry_percentile number nullable
  • industry_average number nullable
  • overall_average number nullable
  • updated_at integer nullable
• salary_history array (default: [])
  • @type string (default: "WantedSalaryPoint")
  • month_date integer required
  • salary number required
• salaries_by_category array (default: [])
  • @type string (default: "WantedCategorySalary")
  • category string required
  • min_salary number nullable
  • max_salary number nullable
  • average_salary number nullable
  • sample_count integer nullable
• headcounts array (default: [])
  • @type string (default: "WantedHeadcount")
  • source string required
  • employee_count integer nullable
  • industry_percentile number nullable
  • history array (default: [])
    • @type string (default: "WantedHeadcountPoint")
    • month_date integer required
    • employee_count integer nullable
    • hired_count integer nullable
    • left_count integer nullable
• service_years array (default: [])
  • @type string (default: "WantedServiceYears")
  • year integer required
  • average_years number nullable
  • all_companies_average_years number nullable
  • industry_average_years number nullable
• sales number nullable
• sales_source string nullable
• sales_industry_percentile number nullable
• financials array (default: [])
  • @type string (default: "WantedFinancialYear")
  • year integer required
  • sales number nullable
  • operating_income number nullable
  • net_income number 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 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.