POST /api/jobkorea/companies/reviews
Price: 10 credits
Get the JobKorea (jobkorea.co.kr) employee review summary of one company by id or URL: overall score, scores for pay, work-life balance, culture, benefits, job security and career growth, the share of reviewers picking each highlight, survey answer distributions (bonus, overtime, leave, welfare and others), percentage gauges, and male and female average salary and tenure
Takes the same id as jobkorea/companies. Category scores are out of 100.
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: "JobkoreaCompanyReviews")company_id string requiredurl string requiredname string nullableindustry string nullableoverall_score number nullablecategory_scores array (default: [])@type string (default: "JobkoreaReviewScore")category string requiredscore number requiredhighlights array (default: [])@type string (default: "JobkoreaReviewHighlight")text string requiredshare number nullablesurvey array (default: [])@type string (default: "JobkoreaReviewQuestion")question string requiredanswers array (default: [])@type string (default: "JobkoreaReviewAnswer")label string requiredshare number nullablegauges array (default: [])@type string (default: "JobkoreaReviewGauge")key string nullablevalue number requiredstatement string nullablegender object nullable@type string (default: "JobkoreaReviewGender")male_share number nullablefemale_share number nullablemale_average_salary number nullablefemale_average_salary number nullablemale_average_tenure_months integer nullablefemale_average_tenure_months integer nullable422 — 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 review page for that company 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.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.