# Japan Dev Scraper: Japan Tech Jobs and Salaries (`getascraper/japan-dev-scraper`) Actor Scrape English-friendly tech jobs from Japan-Dev.com. Extracts job titles, companies, salaries, remote policies, and visa sponsorship straight from each listing's Google Jobs JSON-LD for stable, structured parsing. Drop-in for HubSpot, Salesforce, and Airtable. $1.99 per 1,000 results. - **URL**: https://apify.com/getascraper/japan-dev-scraper.md - **Developed by:** [GetAScraper](https://apify.com/getascraper) (community) - **Categories:** Lead generation, Jobs, Automation - **Stats:** 10 total users, 2 monthly users, 90.3% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.12 / 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. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. 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. Actors are written with capital "A". ## 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. The best way to integrate Actors is as follows. - **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use). - **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`. - **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`. - **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`. - **Any other language** — the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## Japan Dev Scraper

Source-backed Japan tech hiring feed with stable job IDs and changes. Read Japan Dev's public sitemap and JobPosting data for salary bounds, remote and visa evidence, technology tags, and recurring-monitor deltas.
Japan tech, startup, and international hiring • Tokyo Dev, Japan Dev, Wantedly, and Career Cross for tech and international roles
Tokyo Dev English tech jobs & companies	Japan Dev ➤ You are here	Wantedly Startup jobs & culture data	Career Cross Bilingual & visa-context jobs

A monitorable Japan tech hiring feed, not just a one-off pull
Reads Japan Dev's public sitemap and JobPosting JSON-LD for stable job IDs, JPY salary bounds, remote and visa evidence, and technology tags.

🆔 Stable job IDs
Persistent IDs let you monitor the same listing across runs

💴 Salary bounds
JPY minSalary and maxSalary parsed from JobPosting JSON-LD

🛂 Remote and visa evidence
remoteOnly and visaOnly filters backed by source data

🔁 Change-tracking monitor
monitorMode: "changes" flags NEW, UPDATED, and EXPIRED rows

Also returns technology tags, Japanese language labels, and source provenance for every job. Missing source values are omitted rather than filled in. Use `searchQueries`, `locations`, `techTags`, `minSalary`, `maxSalary`, `remoteOnly`, `visaOnly`, and `japaneseLevels` to filter. Use `monitorMode: "changes"` with a stable explicit `stateKey` for recurring deltas. Change rows use `NEW`, `UPDATED`, `REAPPEARED`, `EXPIRED`, and `UNCHANGED`; incomplete scans emit correlated error rows and do not update state. See the repository README for the full input and output contract. ### 🚀 How it works

STEP 1
Set your search
Enter searchQueries, locations, and techTags to target.

STEP 2
Narrow by fit
Apply minSalary, maxSalary, remoteOnly, visaOnly, and japaneseLevels.

STEP 3
Run once or monitor
Run standalone, or set monitorMode: "changes" with a stateKey for recurring deltas.

### ⭐ Enjoying Japan Dev Scraper?

⭐ ⭐ ⭐ ⭐ ⭐
If this feed is saving you from re-checking Japan Dev by hand, tell us about it.
A 5-star rating takes 10 seconds and helps other recruiters and hiring teams tracking Japan tech roles find it. Your feedback also tells us what to build next.

★ Rate this Actor on Apify

# Actor input Schema ## `searchQueries` (type: `array`): Optional OR-matched batch queries across published title, company, description, and tags. ## `locations` (type: `array`): Optional OR-matched city, prefecture, region, or country values published by Japan Dev. ## `techTags` (type: `array`): Keep jobs whose published title or description contains one of these recognized technologies. ## `minSalary` (type: `number`): Keep a job when its published maximum is at least this value. ## `maxSalary` (type: `number`): Keep a job when its published minimum is at most this value. ## `salaryCurrency` (type: `string`): Optional exact currency filter. Currency is never assumed when the source omits it. ## `remoteOnly` (type: `boolean`): Require explicit source evidence for a remote role. ## `visaOnly` (type: `boolean`): Require explicit source evidence for sponsorship, work visa, relocation, or overseas applications. ## `japaneseLevels` (type: `array`): Exact published language labels such as N1, N2, business, native, conversational, or basic. ## `startUrls` (type: `array`): Optional Japan Dev job URLs. Objects may include an inputId for correlated provenance. ## `maxItems` (type: `integer`): Maximum successful job records emitted after filters. ## `sortBy` (type: `string`): Deterministic result ordering. Unknown dates and salaries remain last. ## `sortOrder` (type: `string`): Ascending or descending order for the selected sort field. ## `monitorMode` (type: `string`): snapshot emits current rows with transition labels; changes omits UNCHANGED rows. ## `stateKey` (type: `string`): Stable key for a recurring monitor. Use a different key for each independent search scope. ## `includeUnchanged` (type: `boolean`): In changes mode, include rows whose published fields did not change. ## `includeMarketSummary` (type: `boolean`): Save MARKET\_SUMMARY only when published salary values and currencies exist. ## `proxyConfiguration` (type: `object`): Optional Apify proxy configuration. ## Actor input object example ```json { "searchQueries": [], "locations": [], "techTags": [], "remoteOnly": false, "visaOnly": false, "japaneseLevels": [], "startUrls": [], "maxItems": 25, "sortBy": "jobId", "sortOrder": "asc", "monitorMode": "snapshot", "stateKey": "japan-dev-default", "includeUnchanged": false, "includeMarketSummary": false } ``` # Actor output Schema ## `results` (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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "searchQueries": [], "locations": [], "techTags": [], "japaneseLevels": [], "startUrls": [] }; // Run the Actor and wait for it to finish const run = await client.actor("getascraper/japan-dev-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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "searchQueries": [], "locations": [], "techTags": [], "japaneseLevels": [], "startUrls": [], } # Run the Actor and wait for it to finish run = client.actor("getascraper/japan-dev-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 '{ "searchQueries": [], "locations": [], "techTags": [], "japaneseLevels": [], "startUrls": [] }' | apify call getascraper/japan-dev-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,getascraper/japan-dev-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 ` 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/vP6hbW1MBbaqWKnEv/builds/pkbJ33zhDQ2Mqsdpc/openapi.json