/en_japan/jobs/search

POST /api/en_japan/jobs/search

Price: 20 credits

Search job postings on en-japan (エン転職) by keyword, occupation, area, industry, working-condition features, employment type, minimum annual salary and education, optionally new postings only: title, company, employment type, feature tags, posting period, catch copy, duties, requirements, salary, location and the en-japan writer's note

How to use it

At least one condition besides new_only is required. Pass a returned id to en_japan/jobs for the full posting and the employer's company id.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Free-text keyword (examples: "営業", "エンジニア"; minLength: 1)
• occupation_ids array nullable — en-japan occupation codes (examples: ["101000"])
• area_ids array nullable — en-japan area codes: region, prefecture or city (examples: ["1101"])
• industry_ids array nullable — en-japan industry codes (examples: ["1110"])
• topic_ids array nullable — en-japan feature codes for working conditions (examples: ["101"])
• employment_types array nullable — Employment types (one of: "full_time", "contract", "temporary", "temp_to_perm", "part_time", "outsourcing", "other"; examples: ["full_time"])
• min_annual_salary integer nullable — Minimum annual salary in yen, in steps of 500,000 (examples: 6000000)
• education string nullable — Applicant's highest education; postings open to it (one of: "graduate_school", "university", "technical_college", "junior_college", "vocational_school", "high_school")
• new_only boolean — Only newly posted jobs (default: false)
• count integer required — Max number of results (min: 1; max: 2000)

Response

• @type string (default: "EnJapanJobSearchResult")
• id string required
• url string required
• company_name string nullable
• employment_type string nullable
• tags array (default: [])
• is_pro_interview boolean nullable
• is_new boolean nullable
• published_at integer nullable
• expires_at integer nullable
• catch_copy string nullable
• lead string nullable
• job_description string nullable
• requirements string nullable
• salary string nullable
• work_location string nullable
• images array (default: [])
• writer string nullable
• writer_comment 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 — The entity was not found, or a precondition failed 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.