Engage Scraper: jobs in Japan from en-gage.net

Scrape Engage (en-gage.net), a Japanese job site, from the site's own sitemaps, recently updated jobs first: ad headline, company with its website and logo, prefecture, town and postal code, monthly, hourly, daily or annual pay in JPY with its period, employment type, occupation, work hours, nearest station, telework, tags (年間休日120日以上, 転勤なし...) and the full 募集要項 text. Export to CSV, Excel or JSON, or use the API.

USD 0.69 per 1,000 jobs. No login, no browser.

What you get

• Pay with its period from the page's own pay row: 月給 MONTH, 時給 HOUR, 日給 DAY, 年収 or 年俸 YEAR, amounts in yen. No marker, no period. The annual estimate (想定年収) that the page's structured data gives next to a monthly pay is kept apart in extra.annualIncomeInSchema.
• Ads without structured data too: many part-time ads have none; their pay, place, employment type and description are read from the visible page (extra.noStructuredData).
• Recently updated first, from the whole site: the sitemaps list about 2.2 million job addresses, many of them old ads still online. The Actor reads them newest update first and keeps those updated in the last N days (default 30).
• Company facts in extra: company id, corporate number (法人番号), founding year, tags, hours, nearest station, telework.
• Or paste job page URLs to read just those pages.

Input examples

{ "updatedWithinDays": 30, "maxJobs": 20 }

Part-time jobs in Osaka updated in the last 7 days, new ones only (daily schedule):

{ "updatedWithinDays": 7, "prefectures": ["Osaka"], "employmentType": "part-time", "onlyNewJobs": true }

Example row

From a saved Engage job page (empty fields left out, description shortened, some extra fields left out):

{
  "jobId": "engage:18255559",
  "title": "営業を支える数値管理・経営企画サポート",
  "company": "株式会社パートナー",
  "companyUrl": "https://go-partner.jp/",
  "companyLogoUrl": "https://en-gage.net/api/show_file/logo/1063/2",
  "location": "東京都中央区",
  "city": "中央区",
  "region": "東京都",
  "postalCode": "104-0061",
  "country": "JP",
  "salaryMin": 250000,
  "salaryMax": 300000,
  "salaryCurrency": "JPY",
  "salaryPeriod": "MONTH",
  "salaryText": "月給 25万円 ～ 30万円",
  "employmentType": "FULL_TIME",
  "employmentTypeText": "正社員",
  "category": "経営企画",
  "datePosted": "2026-09-24T08:37:50.000Z",
  "descriptionText": "正社員/未経験OK/学歴不問\n\nーーーーーーーーーー\n■ 仕事内容\nーーーーーーーーーー\n\nITやビジネススキルを磨くサポート事務として、経営数値の管理や営業部門のサポートを担当します。 ...",
  "jobUrl": "https://en-gage.net/user/search/desc/18255559/",
  "sourceBoard": "Engage (en-gage.net)",
  "duplicateKey": "c62a857fefa3f47a",
  "language": "ja",
  "extra": {
    "occupation": "経営企画",
    "chips": [
      "正社員",
      "未経験OK",
      "学歴不問"
    ],
    "tags": [
      "年間休日120日以上",
      "駅から徒歩5分以内",
      "転勤なし",
      "急募！内定まで2週間"
    ],
    "postedLabel": "24日前",
    "nearestStation": "東銀座",
    "workHours": "09:00 ～ 18:00",
    "companyId": "1063",
    "annualIncomeInSchema": {
      "min": 3150000,
      "max": 3750000,
      "currency": "JPY",
      "note": "想定年収 as given in the page's JSON-LD"
    },
    "company": {
      "corporateNumber": "7013301020460",
      "founded": "2003年"
    }
  }
}

Good to know

• Filters other than "Jobs updated in the last N days" run after the job page is read. Engage's area and keyword pages answer robots with a bot challenge, and its search API is not for crawlers, so prefectures, words and employment type are checked on each finished job page (about 1.5 s each). You pay only for jobs saved, but a narrow filter reads many pages for each job it keeps: it is slow, and a run whose filter keeps very few jobs stops early once reading pages costs more than the jobs saved (the run summary says why it stopped).
• The sitemap date is the last update, not the posting date. datePosted comes from the page's structured data; an ad without it has no date, only the page's label (for example 17日前) in extra.postedLabel, never turned into a date. Old ads are still online (some from 2016).
• In our 20-job test the most recently updated jobs were almost all template ads of one staffing employer, whose postal codes end in 0000 as the site gives them.
• Not given: end date, workplace type (only a telework row, kept in extra.telework), apply link (applying uses Engage's own form), skills, experience level (the 未経験OK chip is in extra.chips).
• Text is in Japanese, as the site writes it. A 20-job run took 48 s, so 1,000 jobs take about 40 minutes. Contact blocks and the names of company representatives are never read.

Who uses it

• Recruiters and HR firms in Japan: newly updated jobs by prefecture and employment type every day.
• Pay research: monthly and hourly pay by occupation and prefecture.

Output: one row per job

Every Actor in this family writes the same columns, so you can merge boards in one sheet or database.

Field	What it holds
jobId	The board's own job id
title, company	Job title and hiring company (as the board shows them)
companyUrl, companyLogoUrl	Company page and logo on the board, when given
location, city, region, postalCode, country	Location as shown, and its parts; country is an ISO code (FR, DE, US...)
remote, workplaceType	true/false and remote, hybrid or onsite, only when the board says so
salaryMin, salaryMax, salaryCurrency, salaryPeriod, salaryText	Salary range as numbers, ISO currency, HOUR/DAY/WEEK/MONTH/YEAR; empty when the board gives none (never guessed)
employmentType, employmentTypeText	FULL_TIME, PART_TIME, TEMPORARY, INTERN, APPRENTICE, CONTRACTOR, FREELANCE..., and the board's own wording
experienceLevel, category, skills	When the board gives them
datePosted, validThrough	ISO 8601 dates
descriptionText, descriptionHtml	Full description as plain text and as HTML
applyUrl, jobUrl	Where to apply, and the job's page on the board
sourceBoard, searchLabel, scrapedAt	Which board, which of your searches found it, when
duplicateKey	The same key for the same ad posted on several boards (or reposted): title without (m/w/d) or H/F tags, company without legal form, city, country. Use it to merge results from several of our board Actors
extra	A few fields only this board has

Contact email addresses and phone numbers inside descriptions are removed: this Actor never collects recruiters' personal contact details.

Job alerts: only new jobs, sent where you work

1. Switch on Only new jobs since the last run and schedule the Actor (daily, hourly). It remembers the jobs it has already delivered for the same searches and filters, in a key-value store on your own account (named job-boards-seen-
2. Paste a Slack or Discord webhook (or a Zapier or Make webhook, which can email you) into Send new jobs to. After each run that found new jobs you get one message with the count and up to 10 jobs with their links. Free: the message is never billed.

Apify's own integrations (Google Sheets, email, webhooks) work too.

Pricing

Pay per job saved: USD 0.69 per 1,000 jobs (USD 0.00069 a job), plus USD 0.002 per run start. No monthly rental, no charge for jobs skipped as duplicates, already seen or filtered out. Set a maximum cost per run in Apify and the Actor stops just before it, keeping everything saved so far.

Use it through the API

curl -X POST "https://api.apify.com/v2/acts/usefulapi~engage-japan-jobs-scraper/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"updatedWithinDays":30,"maxJobs":20}'

Python: ApifyClient("YOUR_API_TOKEN").actor("usefulapi/engage-japan-jobs-scraper").call(run_input={...}), then read the dataset items.

Good to know

• Polite by design: one request at a time per site with a pause between requests, and the site's robots.txt is followed. Runs read public job pages only: no login, no candidate profiles or CVs.
• What a run summary tells you: the OUTPUT record has jobs saved per search, jobs skipped (duplicates, seen before, too old) and why a run stopped early, if it did.
• Is it legal? The Actor reads job ads that the board publishes openly, the same pages a job seeker sees. You are responsible for how you use the data (for example, the board's terms and data protection rules in your country).
• Found a problem? Open an issue on the Issues tab: we answer quickly.