POST /api/jobkorea/companies/salaries
Price: 10 credits
Get the JobKorea (jobkorea.co.kr) salary profile of one company by id or URL: average, entry, lowest and highest salary, average tenure, revenue, headcount, yearly average salaries, salaries by job field and position, salary, tenure and share by gender, headcount, tenure and salaries by division, monthly headcount with hires and leavers, the company's salary rank in its industry with the industry's top companies, similar companies with their salaries and up to five open postings of the company
Takes the same id as jobkorea/companies. Salaries and revenue are in KRW, tenure in months.
access-token string requiredtimeout 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)@type string (default: "JobkoreaCompanySalaries")company_id string requiredurl string requiredname string nullableaverage_salary number nullableentry_salary number nullabletenure_months integer nullablerevenue number nullableemployee_count integer nullableyearly_salaries array (default: [])@type string (default: "JobkoreaYearSalary")year integer requiredaverage_salary number nullablemin_salary number nullablemax_salary number nullableindustry_average_salary number nullablegenders array (default: [])@type string (default: "JobkoreaGenderStat")gender string requiredshare number nullableaverage_salary number nullabletenure_months integer nullablesimilar_companies array (default: [])@type string (default: "JobkoreaSimilarCompany")id string nullablename string nullableaverage_salary number nullableentry_salary number nullablerevenue number nullabletenure_months integer nullableemployee_count integer nullableopen_jobs array (default: [])@type string (default: "JobkoreaSalaryOpening")id string requiredurl string requiredlegacy_id string nullabletitle string nullableexperience string nullableexperience_min_years integer nullableeducation string nullablelocation string nullablejob_fields array (default: [])posted_at integer nullableapplication_start_at integer nullableapplication_end_at integer nullablemin_salary number nullablemax_salary number nullableindustry string nullableindustry_salary_rank integer nullableindustry_salary_ranking array (default: [])@type string (default: "JobkoreaIndustrySalaryCompany")rank integer requiredid string nullablename string nullableaverage_salary number nullablejob_field_salaries array (default: [])@type string (default: "JobkoreaJobFieldSalary")job_field string requiredpositions array (default: [])@type string (default: "JobkoreaPositionSalary")position string requiredaverage_salary number nullablemin_salary number nullablemax_salary number nullablemonthly_headcount array (default: [])@type string (default: "JobkoreaMonthlyHeadcount")month_start_at integer requiredemployee_count integer nullablehires integer nullableleavers integer nullabledivisions array (default: [])@type string (default: "JobkoreaSalaryDivision")name string requiredemployee_count integer nullableemployee_share number nullabletenure_months integer nullableyearly_salaries array (default: [])@type string (default: "JobkoreaDivisionYearSalary")year integer requiredaverage_salary number required422 — 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.