/en_japan/companies

POST /api/en_japan/companies

Price: 10 credits

Get an employer's page on en-japan (エン転職): company profile (founding, representative, capital, employees, revenue, business, offices), employee review rating with eight score axes, respondents' average salary and overtime with satisfaction rates, and featured employee reviews

How to use it

Company ids come from en_japan/jobs as company_id. The company's current and past postings are en_japan/companies/jobs.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — en-japan company id or company URL (examples: "551", "https://employment.en-japan.com/comp-551/"; minLength: 1)

Response

• @type string (default: "EnJapanCompany")
• id string required
• url string required
• name string required
• image string nullable
• profile object nullable
  • @type string (default: "EnJapanCompanyProfile")
  • founded string nullable
  • representative string nullable
  • capital string nullable
  • employees string nullable
  • revenue string nullable
  • ordinary_profit string nullable
  • business string nullable
  • offices string nullable
  • affiliates string nullable
  • recruitment_info string nullable
  • website string nullable
  • other_details array (default: [])
    • @type string (default: "EnJapanDetail")
    • label string required
    • text string required
• review_rating number nullable
• review_respondent_count integer nullable
• review_respondent_average_age integer nullable
• review_scores array (default: [])
  • @type string (default: "EnJapanReviewScore")
  • label string required
  • score number required
• respondent_average_annual_salary number nullable
• salary_satisfaction_rate number nullable
• respondent_average_monthly_overtime_hours number nullable
• overtime_satisfaction_rate number nullable
• reviews array (default: [])
  • @type string (default: "EnJapanCompanyReview")
  • category string nullable
  • reviewer string nullable
  • rating number nullable
  • text string nullable
  • posted_at integer nullable
  • as_of_year integer nullable
• review_reply string nullable
• review_reply_at integer nullable
• reviews_url string nullable

Errors

• 422 — company is not an en-japan company id or URL 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 — No company under that id 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.