/levtech/career/companies/jobs

POST /api/levtech/career/companies/jobs

Price: 20 credits

List the jobs of a company on Levtech Career (career.levtech.jp), open and closed, each with its title, salary range, job description, required skills, ideal candidate, job types, employment types, features and nearest station. Returns up to 100 jobs per company.

How to use it

Each result has is_closed; pass a job id to levtech/career/jobs for the full posting.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Company id or URL (examples: "1648", "https://career.levtech.jp/company/detail/1648/"; minLength: 1)
• count integer required — Max number of jobs to return (min: 1; max: 100)

Response

• @type string (default: "LevtechCareerJobRef")
• salary_min number nullable
• salary_max number nullable
• salary_currency string nullable
• id string required
• url string required
• is_closed boolean nullable
• is_new boolean nullable
• remote_work_policy string nullable
• can_work_remotely boolean nullable
• description string nullable
• required_skills string nullable
• ideal_candidate string nullable
• employment_types array (default: [])
• job_types array (default: [])
  • @type string (default: "LevtechCareerLabel")
  • id string nullable
  • name string required
  • category string nullable
• industries array (default: [])
  • @type string (default: "LevtechCareerLabel")
  • id string nullable
  • name string required
  • category string nullable
• skills array (default: [])
• features array (default: [])
• stations array (default: [])
  • @type string (default: "LevtechCareerStation")
  • id string nullable
  • name string required
  • line string nullable
  • prefecture string nullable
• company object nullable
  • @type string (default: "LevtechCareerCompanyRef")
  • id string required
  • url string required
  • name 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 — 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.