# Engage Scraper: en-gage.net Japan Jobs & Pay \[USD 0.69/1K] (`usefulapi/engage-japan-jobs-scraper`) Actor

Scrape Engage (en-gage.net) jobs in Japan from the site's sitemaps, recently updated first: title, company, prefecture, town, pay in JPY with its period, employment type, occupation, hours, nearest station and full description. USD 0.69 per 1,000 jobs.

- **URL**: https://apify.com/usefulapi/engage-japan-jobs-scraper.md
- **Developed by:** [Useful API](https://apify.com/usefulapi) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.69 / 1,000 jobs

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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

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

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

```json
{ "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):

```json
{
  "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-<board>), and saves only
   new ones. The first run delivers everything and remembers it. **Memory name** shares one memory between schedules,
   or starts fresh.
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

```bash
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.

# Actor input Schema

## `startUrls` (type: `array`):

Engage job pages to read directly, for example https://en-gage.net/user/search/desc/18255559/. When given, the Actor reads only these pages and ignores the sitemap options below (the filters still apply).

## `updatedWithinDays` (type: `integer`):

Without job page URLs the Actor takes job addresses from Engage's own sitemaps, newest update first, and keeps those whose sitemap date is within this many days. 0 = no limit (the sitemaps also hold years-old ads that are still online).

## `prefectures` (type: `array`):

Keep only jobs in these prefectures (Tokyo, Osaka, Hokkaido, or 東京都, 大阪府). Engage's sitemaps do not say where a job is, so every job page is read first: a narrow filter reads many pages per job kept (about 1.5 s each).

## `keywords` (type: `array`):

Keep only jobs whose headline, company, occupation, place or description contains one of these words (Japanese works best, for example エンジニア or 介護). The job page is read before the check, so a rare word reads many pages.

## `employmentType` (type: `string`):

Keep only jobs of this type, from the ad's own employment type.

## `maxJobs` (type: `integer`):

Stop after saving this many jobs (across all searches). You pay only for jobs saved.

## `postedWithinDays` (type: `integer`):

Only jobs published in the last N days. 0 = any date.

## `onlyNewJobs` (type: `boolean`):

Remembers the jobs already delivered for these searches (in a key-value store on your account) and saves only jobs not seen before. Ideal for daily or hourly schedules and job alerts. The first run delivers everything and remembers it.

## `stateKey` (type: `string`):

Use the same name on several schedules to share one memory, or a new name to start fresh. Letters, digits, - and \_. Empty = one memory per set of searches.

## `includeDetails` (type: `boolean`):

Reads each job's own page for the full description and extra fields. Turn off for faster runs with list fields only (same price per job).

## `notifyUrl` (type: `string`):

Paste a Slack or Discord webhook link, or a Zapier or Make webhook (which can email you). After each run that saved jobs you get one message with the count and up to 10 jobs with their links. With 'Only new jobs' on and a schedule, this is a free job alert. Not billed.

## `descriptionFormat` (type: `string`):

Plain text, HTML, both, or none (smaller datasets).

## `maxJobsPerSearch` (type: `integer`):

Cap for each search line, so one broad search does not use up the whole run. 0 = no cap.

## `proxyConfiguration` (type: `object`):

Not needed for Engage (en-gage.net) in our tests. Apify datacenter proxy or your own proxies only; residential proxy is not supported.

## Actor input object example

```json
{
  "updatedWithinDays": 30,
  "maxJobs": 20,
  "postedWithinDays": 0,
  "onlyNewJobs": false,
  "includeDetails": true,
  "descriptionFormat": "both",
  "maxJobsPerSearch": 0,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

One row per job, same columns on every board of this family. Download as CSV, Excel or JSON.

## `summary` (type: `string`):

Jobs saved per search, jobs skipped (duplicates, seen before, too old), pages read and why the run stopped early (if it did).

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "updatedWithinDays": 30,
    "maxJobs": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("usefulapi/engage-japan-jobs-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "updatedWithinDays": 30,
    "maxJobs": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("usefulapi/engage-japan-jobs-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "updatedWithinDays": 30,
  "maxJobs": 20
}' |
apify call usefulapi/engage-japan-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,usefulapi/engage-japan-jobs-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/SdCLPPERkrkSc00Mt/builds/8dyln4ixYlAMF9Sst/openapi.json