/en_japan/jobs

POST /api/en_japan/jobs

Price: 20 credits

Get one job posting from en-japan (エン転職), live or expired: title, company, posting period, annual salary range, duties, requirements, hiring background, location, hours, salary, holidays, benefits, selection steps, how to apply, photos with captions, the en-japan interviewer's notes and the company profile

How to use it

Job ids come from en_japan/jobs/search or en_japan/companies/jobs. An expired posting answers with is_expired true and keeps its text; company_id opens the employer on en_japan/companies.

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "EnJapanJob")
• id string required
• url string required
• is_expired boolean required
• company_id string nullable
• company_url string nullable
• company_name string nullable
• company_logo string nullable
• employment_types array (default: [])
• published_at integer nullable
• expires_at integer nullable
• updated_at integer nullable
• valid_through_at integer nullable
• annual_salary_min number nullable
• annual_salary_max number nullable
• salary_period string nullable
• industries array (default: [])
• education_requirements string nullable
• location_regions array (default: [])
• catch_copy string nullable
• lead_text string nullable
• tags array (default: [])
• job_description string nullable
• requirements string nullable
• requirement_tags array (default: [])
• hiring_background string nullable
• employment_type_text string nullable
• work_location string nullable
• working_hours string nullable
• salary string nullable
• holidays string nullable
• benefits string nullable
• department string nullable
• how_to_apply string nullable
• contact string nullable
• interview_location string nullable
• selection_steps array (default: [])
• selection_notes string nullable
• other_details array (default: [])
  • @type string (default: "EnJapanDetail")
  • label string required
  • text string required
• photos array (default: [])
  • @type string (default: "EnJapanPhoto")
  • image string required
  • caption string nullable
• interview_notes array (default: [])
  • @type string (default: "EnJapanInterviewNote")
  • subject string nullable
  • text string required
• interview_comment string nullable
• writer string nullable
• company_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

Errors

• 422 — job is not an en-japan job 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 job posting 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.