POST /api/saramin/jobs
Price: 5 credits
Get Saramin job posting details by id
Get full details of a Saramin job posting by its id. Returns the job title, the hiring company (name and active job count), required experience and education, employment type, salary, position level, working hours, qualification requirements and preferred qualifications, work location (district, full address, coordinates), view and scrap counts, the application deadline and period, required documents, application methods, the hiring process, listed benefits, and the full posting description as text, HTML, and any posting images.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)job string required — Saramin job posting id (rec_idx), or a job URL containing it (examples: "54109376", "https://www.saramin.co.kr/zf_user/jobs/relay/view?rec_idx=54109376"; minLength: 1)@type string (default: "SaraminJob")id string requiredurl string requiredcompany object nullable@type string (default: "SaraminJobCompany")name string nullablecsn string nullableprofile_url string nullableactive_job_count integer nullableexperience string nullableeducation string nullableemployment_type string nullablesalary string nullableposition string nullablework_schedule string nullablerequirements string nullablepreferred string nullablelocation object nullable@type string (default: "SaraminJobLocation")name string nullableaddress string nullablelatitude number nullablelongitude number nullableview_count integer nullablescrap_count integer nullabledday string nullabledeadline string nullableapplication_period string nullablerequired_documents string nullableapply_methods string nullablehiring_process string nullablebenefits array (default: [])description string nullabledescription_html string nullableimages array (default: [])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 — Job posting not found or no longer available 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.