/jobkorea/companies/salaries

POST /api/jobkorea/companies/salaries

Price: 10 credits

Get the JobKorea (jobkorea.co.kr) salary profile of one company by id or URL: average and entry salary, average tenure, revenue, headcount, yearly average salaries, salary, tenure and share by gender, and similar companies with their salaries

How to use it

Takes the same id as jobkorea/companies. Salaries and revenue are in KRW, tenure in months.

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "JobkoreaCompanySalaries")
• company_id string required
• url string required
• name string nullable
• average_salary number nullable
• entry_salary number nullable
• tenure_months integer nullable
• revenue number nullable
• employee_count integer nullable
• yearly_salaries array (default: [])
  • @type string (default: "JobkoreaYearSalary")
  • year integer required
  • average_salary number nullable
  • min_salary number nullable
  • max_salary number nullable
  • industry_average_salary number nullable
• genders array (default: [])
  • @type string (default: "JobkoreaGenderStat")
  • gender string required
  • share number nullable
  • average_salary number nullable
  • tenure_months integer nullable
• similar_companies array (default: [])
  • @type string (default: "JobkoreaSimilarCompany")
  • id string nullable
  • name string nullable
  • average_salary number nullable
  • entry_salary number nullable
  • revenue number nullable
  • tenure_months integer nullable
  • employee_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 company page under that id, or the company publishes no salary information 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.