Worknet Korea Jobs Scraper | 고용24 Job Postings

Collect Korean job postings from Worknet / 고용24 (work24.go.kr), the public employment-service portal: title, company, region, salary, schedule, career, education, closing date and apply link. 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	Worknet posting ID
jobTitle	Job title
companyName	Company name
infoType	Posting type code supplied by the site
region	Work region
salary	Salary text as shown on the posting
careerRequired	Career requirement
education	Education requirement
workSchedule	Work schedule / hours text
closingDate	Closing date (ISO YYYY-MM-DD), when shown
jobUrl	Link to the posting detail page
scrapedAt	ISO 8601 timestamp
parse_confidence	Share of core fields (jobId, jobTitle, companyName, region, jobUrl) that were found, 0 to 1

Cells the posting does not show are null.

How to use

1. Optionally enter a Keyword (matched against job title or company; Korean or English). Leave it empty to browse the latest postings nationwide.
2. Optionally enter a Region (a Worknet work-region code) to narrow results.
3. Set Pages to fetch (10 postings per page) and Max results.
4. Leave Proxy configuration on the default (Apify Residential, Korea). It is already set up; you need no extra account.
5. Click Start, then open the Jobs overview table or export the dataset as JSON, CSV or Excel.

Keyword and region are best-effort filters, so spot-check the first results for your query.

Input

Field	Type	Default	Description
keyword	string	empty	Search term (best-effort filter)
region	string	empty	Worknet work-region code (best-effort filter)
maxItems	integer	100	Maximum postings across all pages (0 = no cap)
pagesToFetch	integer	5	Result pages to walk (1 to 1000, 10 postings per page)
proxyConfiguration	object	Apify Residential, country KR	Proxy settings. Korea is recommended for stable access

Example input:

{
  "maxItems": 100,
  "pagesToFetch": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "KR"
  }
}

With no keyword or region, the actor reads the latest postings nationwide.

Output example

Values below are illustrative.

{
  "jobId": "K150000000000001",
  "jobTitle": "웹 개발자 모집",
  "companyName": "예시주식회사",
  "infoType": "D",
  "region": "서울 강남구",
  "salary": "월급 3,000,000원 이상",
  "careerRequired": "경력 3년 이상",
  "education": "대졸(4년)",
  "workSchedule": "주 5일 근무",
  "closingDate": "2026-10-31",
  "jobUrl": "https://www.work24.go.kr/wk/a/b/1200/empDetailAuthView.do?wantedAuthNo=K150000000000001",
  "scrapedAt": "2026-10-02T09:30:00Z",
  "parse_confidence": 1.0
}

Use cases

• Job aggregation: add Korean public-portal postings to a job board or alert service.
• Labour-market research: compare pay, career and education requirements by region.
• Recruitment sourcing: track new openings with closing dates for planning.
• Regional analysis: follow hiring activity in specific areas using region codes.

FAQ

Do I need an API key or my own proxy? No. No key or login is needed, and the residential proxy (Korea) is built in.

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

What does the region filter expect? A Worknet work-region code. Leave it empty for nationwide results.

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.