Saramin Korea Jobs Scraper | 사람인 채용정보

Collect Korean job postings from Saramin (saramin.co.kr): job title, company, location, career level, education, employment type, skill keywords, closing date and apply link. Search by keyword in Korean or English. Pay per result (see the Pricing tab). The residential proxy is built in.

What data you get

One dataset row per job posting (duplicates are removed by posting ID). Text values are returned in Korean, as shown on the site.

Field	Description
jobId	Saramin posting ID
jobTitle	Job title
jobUrl	Link to the posting on Saramin
companyName / companyUrl	Employer name and its Saramin company page link
location	Work location
experience	Career requirement
education	Education requirement
employmentType	Employment type (for example regular, contract)
salary	Salary text, only when the card shows one; otherwise null
sectors	List of skill / sector keywords
deadline	Closing date text
modifiedDate	Last-modified date (ISO YYYY-MM-DD), when shown
badges	List of badges on the posting
conditionsRaw	List of the raw condition labels shown on the card
query	The search keyword that found the posting (null when browsing)
scrapedAt	ISO 8601 timestamp
parse_confidence	Share of core fields (jobId, jobTitle, companyName, location, jobUrl) that were found, 0 to 1

How to use

1. Enter one or more keywords in Search keywords (job title, company or skill; Korean or English). Each keyword is searched separately and the results are merged. Leave it empty to browse the latest postings.
2. Set Pages to fetch per keyword (40 postings per page), Max results and Sort order.
3. Leave Proxy configuration on the default (Apify Residential, Korea). It is already set up; you need no extra account.
4. Click Start, then open the Jobs overview table or export the dataset as JSON, CSV or Excel.

Input

Field	Type	Default	Description
searchTerms	array of strings	["Python"] (prefill)	Keywords to search. Empty = browse the latest postings
pagesToFetch	integer	3	Result pages per keyword (1 to 1000, 40 postings each)
maxItems	integer	100	Maximum postings across all keywords and pages (0 = no cap)
sort	string	relation	relation (relevance), reg_dt (latest first) or accuracy
proxyConfiguration	object	Apify Residential, country KR	Proxy settings. Korea is recommended for stable access

Example input:

{
  "searchTerms": ["Python"],
  "pagesToFetch": 3,
  "maxItems": 100,
  "sort": "relation",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "KR"
  }
}

Output example

Values below are illustrative.

{
  "jobId": "12345678",
  "jobTitle": "백엔드 개발자 (Python)",
  "companyName": "예시테크",
  "companyUrl": "https://www.saramin.co.kr/zf_user/company-info/view?csn=0000000000",
  "location": "서울 강남구",
  "experience": "경력 3년↑",
  "education": "대졸↑",
  "employmentType": "정규직",
  "salary": null,
  "sectors": ["Python", "Django", "AWS"],
  "deadline": "~ 11/15(토)",
  "modifiedDate": "2026-10-01",
  "badges": ["간편지원"],
  "conditionsRaw": ["서울 강남구", "경력 3년↑", "대졸↑", "정규직"],
  "jobUrl": "https://www.saramin.co.kr/zf_user/jobs/relay/view?rec_idx=12345678",
  "query": "Python",
  "scrapedAt": "2026-10-02T09:30:00Z",
  "parse_confidence": 1.0
}

Use cases

• Job aggregation: bring Korean tech and non-tech listings into a global job board.
• Labour-market research: compare locations, career levels, education and employment types for a skill.
• Skill demand tracking: count sectors keywords across postings.
• Recruitment and expansion research: see who is hiring in Korea and for what.

FAQ

Do I need an API key or my own proxy? No. The residential proxy (Korea) is built in, and no login is needed. You do not need any API keys or external accounts.

How is it priced? Pay per result. See the Pricing tab for the current price per posting.

Is the data in Korean? Values are returned as shown on the site, so labels such as location, education and employment type are in Korean. Keywords can be Korean or English.

Is there a limit for free-plan runs? Runs on a free Apify plan return a preview of up to 25 results. Paid plans have no preview limit.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.