/mynavi/companies

POST /api/mynavi/companies

Price: 5 credits

Get a Mynavi Tenshoku (マイナビ転職) company profile (会社概要) by its numeric company id (or company/job URL): company name, recruitment website, business description, founding date, capital, employee count, representative, head-office address, benefits, first-year income, model salary, the number of active job postings and the list of their jobinfo slugs.

How to use it

Fetch a single Mynavi Tenshoku (マイナビ転職) company profile by its numeric company id (e.g. '402573'), a /company/{id}/ URL, or a jobinfo slug (the company id is the first number in the slug). Returns one item with id, url, name, website, business, established, capital, employee_count, representative, address, benefits, first_year_income, model_salary, active_job_count and job_ids (jobinfo slugs usable with the job get-by-id endpoint).

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "MynaviCompany")
• id string required
• url string required
• name string nullable
• website string nullable
• business string nullable
• established string nullable
• capital string nullable
• employee_count string nullable
• representative string nullable
• address string nullable
• benefits string nullable
• first_year_income string nullable
• model_salary string nullable
• active_job_count integer nullable
• job_ids array (default: [])

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 — Company not found (well-formed id but the company page does not exist) 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.