/mynavi/jobs

POST /api/mynavi/jobs

Price: 10 credits

Get a Mynavi Tenshoku (マイナビ転職) job posting by its jobinfo slug (or job URL): job title and catch copy, employment type, job category and industry, posted/expiry dates, full job description, candidate requirements, salary text and min/max annual salary, first-year income, raises and bonuses, allowances, working hours, work location and structured locations, access, nearest station, holidays, benefits, planned hiring count, feature tags, application method, post-application contact timeline, document screening points, selection process, interview count and location, the recruiter inquiry block (company, address, phone, contact person), images, and the hiring company (name, website, industry, founding date, capital, employee count, representative, revenue, business description, head-office address).

How to use it

Fetch a single Mynavi Tenshoku (マイナビ転職) job posting by its jobinfo slug (e.g. 'jobinfo-402573-1-12-1') or a full job URL. Returns one item with id, display_id, url, title, catch_copy, employment_type, job_category, industry, posted_at, valid_through, description, requirements, salary, salary_min, salary_max, first_year_income, raise_bonus, allowances, work_hours, work_location, locations, access, nearest_station, holidays, benefits, hiring_count, features, application_method, response_after_application, screening_points, selection_process, interview_count, interview_location, a nested inquiry object (company, address, phone, contact), image/images and a nested company object.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Mynavi Tenshoku job posting as a jobinfo slug or a full job URL (examples: "jobinfo-402573-1-12-1", "https://tenshoku.mynavi.jp/jobinfo-402573-1-12-1/"; minLength: 1)

Response

• @type string (default: "MynaviJob")
• id string required
• display_id string nullable
• url string required
• catch_copy string nullable
• employment_type string nullable
• job_category string nullable
• industry string nullable
• posted_at string nullable
• valid_through string nullable
• description string nullable
• requirements string nullable
• salary string nullable
• salary_min integer nullable
• salary_max integer nullable
• first_year_income string nullable
• raise_bonus string nullable
• allowances string nullable
• work_hours string nullable
• work_location string nullable
• locations array (default: [])
• access string nullable
• nearest_station string nullable
• holidays string nullable
• benefits string nullable
• hiring_count string nullable
• features array (default: [])
• application_method string nullable
• response_after_application string nullable
• screening_points string nullable
• selection_process string nullable
• interview_count string nullable
• interview_location string nullable
• inquiry object nullable
  • @type string (default: "MynaviJobInquiry")
  • company string nullable
  • address string nullable
  • phone string nullable
  • contact string nullable
  • text string nullable
• image string nullable
• images array (default: [])
• company object nullable
  • @type string (default: "MynaviJobCompany")
  • id string nullable
  • name string nullable
  • url string nullable
  • website string nullable
  • industry string nullable
  • established string nullable
  • capital string nullable
  • employee_count string nullable
  • representative string nullable
  • revenue string nullable
  • business string nullable
  • address string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Job posting not found (well-formed slug but the job page does not exist or has been taken down) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.