Mynavi Tenshoku Jobs Scraper (Japan)

Scrape job listings from Mynavi Tenshoku (マイナビ転職, tenshoku.mynavi.jp), one of Japan's largest mid-career job boards, and get one flat row per job: no nested objects, no HTML to strip yourself. Walk the whole-site feed (about 63,000 open jobs on 2026-10-01) or any prefecture, and get title, company, location, salary text with a parsed yen range, expected first-year income, employment type, condition tags and listing dates.

Input

field	meaning
startUrls	Mynavi Tenshoku list pages to walk - any tenshoku.mynavi.jp URL with a /list/ path, e.g. https://tenshoku.mynavi.jp/list/ (the whole-site feed). Each page is followed forward through its own 次へ (next) link until the last page or maxItems
areas	Optional prefecture / overseas-region codes (p13 = 東京, p27 = 大阪, a20 = アジア, ...), resolved to the same list links the site's own area menu uses
maxItems	Stop after this many jobs in total, shared across every start page in order. A list page carries 50 job cards
proxyConfiguration	Apify's default (datacenter) proxy - see Proxy below

Leave startUrls and areas both empty to walk the whole-site feed.

What is not an input, and why

• Keyword search. The site's search box submits a form by POST and pages its results through a second POST form; neither leaves a link on the page that this actor could follow. Rather than guess at a URL shape, the actor accepts list URLs only.
• Hokkaido as an area. The site's area menu links 北海道 only to a regional landing page, not to a /list/ page, so there is no menu link to reuse. If you have a Hokkaido list URL, pass it in startUrls.

Output

field	meaning
job_id	The id in the job's permalink, e.g. 206871-1-5-1 (jobinfo-<id>/). One row per id per run
url	https://tenshoku.mynavi.jp/jobinfo-<id>/
job_key	Mynavi's internal numeric posting key, from the card's 気になる button
company_id	The first part of job_id; the same number names the company's image folder
title	Job headline
company	Company name - the part of the card heading before |
company_tagline	The company's catch line after |, if the heading has one
featured	true for the 注目 (featured) placements Mynavi shows ahead of the feed
badge	The card's corner label as printed: 新着 (new) or 注目 (featured)
employment_type	正社員, 契約社員, ... as printed
tags	Condition chips on the card: 転勤なし, 学歴不問, リモートワーク可, 志望動機・自己PR不要, ...
location	勤務地 text
salary_text	給与 text, as printed
salary_period, salary_min_yen, salary_max_yen	Parsed from salary_text - see below
first_year_income_text, first_year_income_min_yen, first_year_income_max_yen	初年度年収 (expected first-year annual income), e.g. 550万円～600万円 -> 5,500,000 / 6,000,000
job_description	仕事内容 text
target_candidates	対象となる方 text
updated_date	情報更新日 (listing last updated), ISO date
listing_end_date	掲載終了予定日 (scheduled end of the listing), ISO date
logo_url, image_url	Company logo and the card's banner photo
list_position	The card's position on its list page
source_url	The list page the row was read from

Every field comes from the list page itself; the actor does not open each job's detail page. Mynavi shortens long text cells on the list page and ends them with … - location, salary_text, job_description and target_candidates carry exactly what the list page prints, so the full text is on the job's own page.

null is not zero

A field is null when the card does not state it, never a stand-in value:

• salary_min_yen / salary_max_yen / salary_period are filled only when the salary text opens with one figure or one range, e.g. 月給230,000円〜400,000円 -> monthly 230,000 / 400,000. Mynavi's salary text is free text and often lists several tiers -

  【未経験者の場合】 月給28万円〜 【経験者の場合】 月給39万円〜
  , or a different figure per city. Picking one tier would be a guess, so those rows keep the words in salary_text and the numbers stay null. On the 2026-10-04 sample, roughly a third of cards were of that kind.
• salary_max_yen is null for an open-ended salary (月給35万円以上, 月給29万円〜). A single exact figure (月給266,228円) fills both min and max.
• first_year_income_* is null when the card has no 初年度年収 row - 8 of 49 complete cards on 2026-10-04.
• logo_url is null on cards that print no company logo - 15 of 50 on 2026-10-01, 14 of 50 on 2026-10-04 - and on every row from an areas start: the prefecture / region list pages use a different card that has no logo.
• Area pages (areas) carry the same fields otherwise. Their 初年度年収 is printed as 450～900万円 and parsed the same way; on 2026-10-04, 5 of 50 東京 cards had none. The overseas region pages (a20-a25) also list scouting.mynavi.jp postings, which are not tenshoku jobs and have no job_id; those are skipped and not charged (43 of 50 cards on the 中近東・アフリカ page, 2026-10-04).
• job_key, updated_date, listing_end_date were printed on every complete card sampled; they are nullable only so that a card missing them is still a row rather than a crash.

A 0 in any of these columns would read as a measurement ("unpaid", "no income") when the truth is that the card did not say.

Proxy

Apify's default proxy (datacenter) is the default, and residential is not needed: the probes on 2026-10-01 and 2026-10-04 fetched full list pages from a datacenter address. Refusals (HTTP 403, 429, 5xx, or a page with neither job cards nor a pager) are retried from a fresh proxy address; a 404 is treated as permanent and not retried.

Billing

Pay per event: $0.00062 per job, plus a fixed actor-start fee per run. A job is charged once per run, even when it appears on more than one page or under more than one start URL. Platform usage is included.