Townwork Jobs Scraper — Japan Part-Time & Casual (Arubaito) Jobs

Scrape part-time, casual and arubaito (アルバイト) job listings from Townwork (townwork.net), Recruit's nationwide Japanese part-time job board. Search by keyword or paste any Townwork area/search URL, paginate the full result set, and get a clean, flat record per job: title, employer, wage (with period and parsed min/max in JPY), employment type, nearest station, job URL and a machine-readable parse_confidence score on every row.

This Townwork Jobs Scraper is built for recruiters, HR-tech products, wage-benchmark and labor-market analysts, and lead-generation pipelines that need structured Japanese part-time hiring data without maintaining a fragile in-house scraper.

What Townwork job data you get

Every result row contains:

• job_id — Townwork's stable listing id
• title — the job title, exactly as posted in Japanese (e.g. 高級喫茶店でのホール)
• company — hiring company / store name
• salary_text — the wage label exactly as Townwork shows it (e.g. 時給1,350円以上)
• salary_period — normalized wage period: hourly (時給), daily (日給), weekly (週給), monthly (月給), annual (年俸/年収)
• salary_min / salary_max — wage bounds parsed to integers in JPY (salary_max is null on 以上 / "from X" listings that quote no upper bound)
• currency — always JPY
• employment_type — アルバイト・パート, 業務委託, 契約社員, etc.
• access — nearest station and walk time (e.g. 渋谷駅から徒歩1分), when shown
• url — canonical link to the job detail page on townwork.net
• area — optional free-text label you set, stamped on every row for provenance
• description — full job description text (optional, enable "Include full job descriptions")
• parse_confidence — quality signal per row (fraction of core fields present), so you can filter incomplete records programmatically

How to scrape Townwork jobs

1. Enter a keyword (Japanese or English) — e.g. カフェ, コンビニ, warehouse. The actor builds the Townwork keyword search for you.
2. Or paste one or more Townwork search / area URLs copied straight from the site (e.g. a prefecture page like https://townwork.net/prefectures/tokyo/job_search/ma-013001/). Each is paginated independently.
3. Set Pages per query to go deeper (Townwork shows ~20 listings per page) and Max total items to cap cost (default 100).
4. Optionally enable Include full job descriptions to fetch each listing's detail page.
5. Run. Results stream into the dataset as they are scraped.

The actor paginates automatically and de-duplicates by job_id until every matching job is collected or your maxItems cap is reached.

How much does it cost?

Pay per result — there is no subscription. You are billed $4.05 per 1,000 jobs returned ($0.00405 per job). A typical 100-job trial run costs about $0.41. If you enable Include full job descriptions, each enriched listing adds a separate $0.005 event (charged only for the listings you fetch descriptions for). The actor runs on Apify's RESIDENTIAL proxy, billed to your own Apify account — there is no extra proxy fee from us and no key to supply.

Example output

{
  "job_id": "79704e42ed0623a4",
  "title": "高級喫茶店でのホール",
  "company": "珈琲茶館 集　プレミアム渋谷駅前店",
  "salary_text": "時給1,350円以上",
  "salary_period": "hourly",
  "salary_min": 1350,
  "salary_max": null,
  "currency": "JPY",
  "employment_type": "アルバイト・パート",
  "access": "渋谷駅から徒歩1分",
  "url": "https://townwork.net/viewjob/jobid_79704e42ed0623a4/",
  "parse_confidence": 1.0
}

Why this Townwork Jobs Scraper

• Resilient rendering, not brittle class names — the parser anchors on stable DOM structure, so it keeps working through Townwork's front-end redesigns.
• Normalized wages — salary_period, salary_min and salary_max are parsed for you from the raw Japanese label, ready for filtering and benchmarking.
• Quality signal built in — parse_confidence lets you trust the data and drop incomplete rows automatically.
• Keyword or URL — start from a plain keyword or paste any Townwork area/search page; mix and match.
• Apify Proxy, pay-per-result — runs on Apify's RESIDENTIAL proxy by default for reliable access; you pay only per result, no monthly fee.

FAQ

Do I need a Townwork login or API key? No. The actor reads public Townwork listing pages.

Can I get full job descriptions? Yes — enable "Include full job descriptions". Each job then makes one extra request to its detail page (slower, richer output, billed as a separate event).

How fresh is the data? It is fetched live on every run, directly from townwork.net.

Is the wage always present? Townwork shows a wage on essentially every listing, so salary_text is near-universal. salary_max is null when the listing quotes a single "from X" (以上) figure with no upper bound — that is correct, not missing data.

Is this legal? The actor collects only publicly visible job-listing data that Townwork shows to any visitor. Use it in compliance with Townwork's terms and applicable law.

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.