# en-japan Jobs Scraper (Japan) (`superslowsloth/enjapan-jobs`) Actor

Scrape job listings from employment.en-japan.com (エン転職), a major Japanese mid-career job board: job id and URL, title, company, location, salary text with yen band where stated, employment type, tags - by area, occupation, keyword or new arrivals.

- **URL**: https://apify.com/superslowsloth/enjapan-jobs.md
- **Developed by:** [Superslow Sloth](https://apify.com/superslowsloth) (community)
- **Categories:** Jobs, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.10 / 1,000 job scrapeds

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

## en-japan Jobs Scraper (Japan)

Scrape job listings from [en-japan](https://employment.en-japan.com) (エン転職),
one of Japan's major mid-career job boards, and get one flat row per job: id and
URL, title, company, location, salary as printed (plus a yen band when the text
states one), employment type, badges and the job text on the card. Japanese
text is kept exactly as en-japan prints it.

Run it for an area (Tokyo is `23`), an occupation, a keyword, the day's new
arrivals, or paste any search you built on the site.

### Example input

```json
{
    "areaIds": ["23"],
    "newOnly": true,
    "maxItems": 500
}
```

That is the daily feed: the Tokyo jobs en-japan flags as new arrivals (526 of
Tokyo's 6,266 on 2026-10-23). To read a whole area past the ceiling below,
list occupations too:

```json
{
    "areaIds": ["23"],
    "occupationIds": ["100000", "150000"],
    "maxItems": 4000
}
```

### Input

| field | meaning |
|---|---|
| `searchUrls` | Optional. en-japan search result URLs on `https://employment.en-japan.com/search/search_list/`, copied from your browser after setting conditions on the site. Every condition is kept; the actor manages the page number. When given, the four filter fields below are ignored |
| `areaIds` | Optional. en-japan area ids (Tokyo is `23`). Each area is its own search |
| `occupationIds` | Optional. en-japan occupation ids: `100000` is the whole sales group (営業系), `101000` corporate sales (法人営業), `150000` planning, clerical, marketing and admin. Each occupation is its own search, combined with each area |
| `keyword` | Optional. A keyword searched across the job text |
| `newOnly` | Only jobs en-japan flags as new arrivals (its 新着のみ filter) |
| `fetchDetails` | Open every job's detail page to fill `posted_from`, `posted_until` and `last_updated`. One extra request per job; off by default |
| `maxItems` | Stop after this many jobs in total, shared across all searches. en-japan shows 50 jobs per page |
| `proxyConfiguration` | Apify datacenter proxy by default - see **Proxy** below |

At least one of `searchUrls`, `areaIds`, `occupationIds`, `keyword` or
`newOnly` is required: en-japan answers a search with no condition with an
empty page, so the actor refuses it rather than report "zero jobs". An id the
site does not know is ignored by the site, not rejected; check the first rows.

### Output

| field | meaning |
|---|---|
| `job_id` | en-japan's numeric job id, from the `/desc_<id>/` part of the job URL (a string) |
| `url` | The job's detail page on employment.en-japan.com |
| `title` | The job headline |
| `company` | Company name as printed |
| `employment_types` | The employment-type badges, e.g. `["正社員"]`; a card can carry two or three |
| `tags` | The other badges: 職種未経験OK, 転勤なし, 完全週休2日, エン エージェント求人 ... |
| `catch_copy` | The headline sentence above the card's photo |
| `teaser` | The opening of the job text beside the photo (en-japan cuts it with "……") |
| `job_summary` | The card's 仕事内容 (work) row |
| `requirements` | The card's 応募資格 (who it is for) row |
| `salary_text` | The card's 給与 (salary) row as printed |
| `salary_min_jpy`, `salary_max_jpy` | Yen, only when `salary_text` states exactly one band or floor - see below |
| `salary_period` | `year` for a 年収 / 年俸 band, `month` for a 月給 band, `null` when there is no band |
| `location` | The card's 勤務地 (work location) row |
| `company_feature` | The card's 会社の特徴 row, printed only on エン エージェント cards |
| `editor_comment` | The reporter's comment in the card's 取材 box |
| `image_url` | The card's first photo |
| `posted_from`, `posted_until`, `last_updated` | ISO dates from the detail page; only with `fetchDetails` |
| `search_url` | Which search produced this row (page number stripped) |

Long rows are cut by en-japan on the search page with "…" or "……"; this actor
returns them as printed. Turn on `fetchDetails` only for the three date
columns - it does not add the full job text.

#### Which fields can be `null`, and why `null` is not zero

Counts are from the 2,005 cards on the 40 pages of Tokyo results read on
2026-10-23.

- **`salary_min_jpy` / `salary_max_jpy` / `salary_period`** are `null` on 907
  of 2,005 cards. A value is filled only when the salary text states exactly
  one band or floor next to a period word, such as "月給28万円～40万円" or
  "年収500万円以上". Two bands ("東京：月給21万円～／大阪：月給19.7万円～"), example
  incomes ("月収例25.6万円") and a bare "350万円～550万円" with no period word are
  not one band for one period, so they stay `null`. A floor has no maximum, so
  `salary_max_jpy` is also `null` on those. A `0` would read as "unpaid" and an
  invented band as a measurement.
- **`posted_from` / `posted_until` / `last_updated`** are `null` unless you set
  `fetchDetails`, because the search results print no date of any kind. They
  are also `null` for a job whose detail page could not be read (the row is
  still returned, and the run log says which job).
- **`catch_copy`** (367 null) and **`teaser`** (436 null): cards that print
  none. **`company_feature`** is null on every card that is not an エン
  エージェント one. **`image_url`** is null on 518 cards with no photo.
- **`job_summary`, `requirements`, `salary_text`, `location`** are `null` when
  the card has no row with that label; every measured card had them except one
  without a salary row.

### The 2,000-job ceiling

en-japan serves at most **40 pages of 50 (2,000 jobs) for any single search**,
however many it reports. Tokyo says 6,266 jobs; the pages after the 40th come
back empty. The actor reads each search until it ends and, when a search stops
at the ceiling, says so in the run log and the run's status message. To read
past it, split the search: give several `occupationIds` (each is its own search
of up to 2,000), several `areaIds`, or use `newOnly` for a daily feed that
stays well under it. A job found by two of your searches is returned and
charged once.

The first page of a search also shows about five sponsored cards whose jobs
reappear later in the results; they are returned once, not twice.

### Proxy

The default is Apify's datacenter proxy: on 2026-10-23 a probe from the
platform got a full results page from 10 of 10 datacenter exits (residential
9 of 10, Japanese residential 9 of 10). Residential exits are not needed and
cost more.

### Billing

Pay per event: **$0.0021 per job** (`job-scraped`), plus a small
**actor-start** fee ($0.002) per run. Each job is charged once, after it has
been written to the dataset. The same job id is never charged twice in one run,
even when two of your searches both return it. `fetchDetails` does not change
the price per job.

# Actor input Schema

## `searchUrls` (type: `array`):

Optional. en-japan search result URLs, copied from your browser after setting conditions on employment.en-japan.com - they must be on https://employment.en-japan.com/search/search_list/ and carry at least one condition. Every condition in the URL is kept; the page number is managed by the actor. When you give URLs, the area, occupation, keyword and new-arrivals fields below are ignored. All URLs share the maxItems budget, in the order given.

## `areaIds` (type: `array`):

Optional. en-japan area ids, e.g. 23 for Tokyo. Each area is its own search. Used only when Search URLs is empty. An id en-japan does not know is ignored by the site: on its own the search then returns no jobs, next to other conditions it returns jobs from every area.

## `occupationIds` (type: `array`):

Optional. en-japan occupation ids, e.g. 100000 for the whole sales group (営業系) or 101000 for corporate sales (法人営業). Each occupation is its own search (combined with each area), which is how to read past the 2,000-job ceiling en-japan puts on any single search. Used only when Search URLs is empty. An id en-japan does not know is ignored by the site and returns the unfiltered search.

## `keyword` (type: `string`):

Optional. A keyword searched across en-japan job text, e.g. エンジニア. Used only when Search URLs is empty.

## `newOnly` (type: `boolean`):

Keep only jobs en-japan flags as new arrivals (its 新着のみ filter). This is the daily-feed switch: a Tokyo search that returns 6,266 jobs returned 526 with it on. Used only when Search URLs is empty.

## `fetchDetails` (type: `boolean`):

Open every job's detail page to fill posted_from, posted_until and last_updated, which the search results do not show. Costs one extra request per job, so runs are slower; the price per job is unchanged. Off by default: those three columns are then null.

## `maxItems` (type: `integer`):

Stop after this many jobs in total, shared across every search. en-japan shows 50 jobs per page, so every 50 jobs is one page request. A single search never returns more than 2,000 jobs, however many en-japan reports.

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

Apify datacenter proxy is the default: employment.en-japan.com answered datacenter exits with full pages on 2026-10-23. Residential is not needed and costs more.

## Actor input object example

```json
{
  "searchUrls": [
    "https://employment.en-japan.com/search/search_list/?areaid=23&refine=1"
  ],
  "areaIds": [
    "23"
  ],
  "newOnly": false,
  "fetchDetails": false,
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `jobs` (type: `string`):

No description

# 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 = {
    "searchUrls": [
        "https://employment.en-japan.com/search/search_list/?areaid=23&refine=1"
    ],
    "areaIds": [
        "23"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("superslowsloth/enjapan-jobs").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 = {
    "searchUrls": ["https://employment.en-japan.com/search/search_list/?areaid=23&refine=1"],
    "areaIds": ["23"],
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("superslowsloth/enjapan-jobs").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 '{
  "searchUrls": [
    "https://employment.en-japan.com/search/search_list/?areaid=23&refine=1"
  ],
  "areaIds": [
    "23"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call superslowsloth/enjapan-jobs --silent --output-dataset

```

## MCP server setup

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

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/QVnfDbeC5y6XMgYMB/builds/xqHr4VJ0RKdRnM4SQ/openapi.json