# Green Japan Jobs Scraper (`stone_jadex/green-japan-jobs-scraper`) Actor

Public Green (green-japan.com) IT and startup jobs from prefecture, industry, and salary listing pages. Title, company, salary, location, and optional full description. Draft price $0.0015 per job ($1.50 per 1,000). No start fee. Does not use robots-disallowed search, API, or photo paths.

- **URL**: https://apify.com/stone_jadex/green-japan-jobs-scraper.md
- **Developed by:** [Stone Jade](https://apify.com/stone_jadex) (community)
- **Categories:** Jobs
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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

## Green Japan Jobs Scraper

Collect public Green listings for Japan recruiting and hiring-market research. Use area, industry or salary pages, prefecture IDs or direct job URLs to select the market you want to inspect.

### What you gain

- Compare job titles, company names, prefectures and disclosed salary ranges.
- Review remote tags and employment type alongside openings where Green provides them.
- Add requirements, benefits and working hours from detail pages when available.
- Use company identifiers and job links to follow up on relevant employers.

### Ways to use the data

- A Japan recruiter can assemble an area-specific shortlist of engineering roles and inspect the requirements.
- A talent researcher can compare published salary and remote-work language across selected employers.

### Delivery preview

These fictional rows are **illustrative**, not captured results. Fields may be missing in actual records.

| Role | Company | Prefecture | Salary | Work style |
|---|---|---|---|---|
| Engineer | Example Tech | Tokyo | JPY 6,000,000 / year | Remote |
| Designer | Example Studio | Osaka | Not published | Hybrid |
| Product Manager | Example Labs | Tokyo | JPY 7,000,000 / year | On-site |

### Why choose this Actor

- Start from Green area, industry or salary listings, or use optional sitemap discovery.
- List records support initial screening; optional detail adds job requirements, benefits and company context.

### Pricing

Prices in **USD**, verified on 4 November 2026. Check the current Pricing tab before running.

| Result type | Event price |
| --- | ---: |
| Job result | $1.5 per 1,000 results |
| Job with details | $1.5 per 1,000 results |

The detail event replaces the list event for the same result; the two are not added together. For example, 1,000 results at the job result rate incur $1.5 in result-event charges. This calculation covers Actor event charges. Review Pricing for any separately listed platform usage; later access to stored data follows Apify's applicable storage pricing.

### Try it in three steps

1. Provide a Green area, industry, salary or job URL, or prefecture IDs.
2. Set `maxItems` and enable `scrapeDetails` for job-page information.
3. Run the Actor, review the dataset and export the results in your preferred available format.

### Coverage and FAQ

**What are the limits?** Coverage depends on the supplied pages or sitemap and available source data. Details can fail, and published fields such as salary may be missing.

**Is this a live feed or an alert service?** Each run captures data available at that time. Repeated collection and any comparison, alerting or decisions require your own workflow.

**Will every field be populated?** No. The source may omit values, change a page or restrict access; check the original record before relying on it. A configured maximum does not guarantee that many results.

# Changelog

This Actor's version history is a separate document: https://apify.com/stone_jadex/green-japan-jobs-scraper/changelog.md

# Actor input Schema

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

Public Green listing pages such as https://www.green-japan.com/area/13, https://www.green-japan.com/industry_h/120, or https://www.green-japan.com/salary/400, or a job URL https://www.green-japan.com/company/{id}/job/{id}. /search, /api/v2, and /photo are disallowed by robots.txt and rejected. Empty uses Tokyo (area 13) unless prefectureIds or useSitemaps is set. Without login each entry URL gives at most 3 pages (about 60 jobs), so 1,000+ jobs need at least 17 distinct entry URLs (aim for 25–30 to absorb duplicates across areas/industries) or useSitemaps.

## `prefectureIds` (type: `array`):

Each id becomes https://www.green-japan.com/area/{id}. 1 is Hokkaido, 13 is Tokyo, 47 is Okinawa. Green shows anonymous visitors at most 3 pages (about 60 jobs) per listing URL; page 4+ redirects back to page 3 with a sign-up prompt. For 1,000+ jobs, list many prefectures and turn on useSitemaps.

## `useSitemaps` (type: `boolean`):

Recommended for large runs. Reads sitemap.xml and only areas, big_industries, small_industries, and salaries. Opens only as many listing pages as Max jobs needs (about 20 jobs each). Does not open job or company sitemap shards. Each listing URL yields at most about 60 jobs (3 pages) without login, so the sitemaps (112 listing URLs (49 area + 9 big-industry + 39 small-industry + 15 salary pages, counted 2026-10-26)) are the way to reach 1,000+ jobs.

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

Stop after this many jobs. One listing page contains about 20, and each listing URL shows at most 3 pages (about 60 jobs) without login.

## `scrapeDetails` (type: `boolean`):

Adds description, requirements, benefits, hours, holidays, selection process, address, and public company facts. Charged as job-detail instead of job, at the same price. Off by default so a run stays on listing pages.

## `requestDelayMs` (type: `integer`):

Pause between requests in milliseconds. Higher values are gentler on the site.

## `maxRunSeconds` (type: `integer`):

Stops cleanly and writes OUTPUT before this limit.

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

Direct connection by default. Green listing pages are public HTML.

## `useProxyFallback` (type: `boolean`):

If direct requests get blocked, retry through Apify Proxy.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.green-japan.com/area/13"
    }
  ],
  "prefectureIds": [
    "13"
  ],
  "useSitemaps": false,
  "maxItems": 20,
  "scrapeDetails": false,
  "requestDelayMs": 1000,
  "maxRunSeconds": 3600,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "useProxyFallback": false
}
```

# Actor output Schema

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

Public Green job records saved in the default dataset, including the uncharged run-notice row when a run stops early.

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

Crawl statistics, parsed seeds, errors, robots and HTTP status, and the reason the run stopped, stored under the OUTPUT key.

# 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 = {
    "startUrls": [
        {
            "url": "https://www.green-japan.com/area/13"
        }
    ],
    "prefectureIds": [
        "13"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("stone_jadex/green-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 = {
    "startUrls": [{ "url": "https://www.green-japan.com/area/13" }],
    "prefectureIds": ["13"],
}

# Run the Actor and wait for it to finish
run = client.actor("stone_jadex/green-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 '{
  "startUrls": [
    {
      "url": "https://www.green-japan.com/area/13"
    }
  ],
  "prefectureIds": [
    "13"
  ]
}' |
apify call stone_jadex/green-japan-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,stone_jadex/green-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/Kupdq7tupbuzug1bY/builds/RK3buLfODLccup7et/openapi.json