POST /api/levtech/career/jobs
Price: 20 credits
Get one job on Levtech Career (career.levtech.jp): the full posting with job description, required and preferred skills, salary range, employment types, job types, skills, industries, work locations, working hours, overtime, holidays, remote work and side job rules, benefits, selection details, the hiring company and its other jobs. Closed postings are returned with is_active false.
Find job ids with levtech/career/jobs/search or levtech/career/companies/jobs; pass company.id to levtech/career/companies for the company profile.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)job string required — Job id or URL (examples: "581448", "https://career.levtech.jp/engineer/offer/detail/581448/"; minLength: 1)@type string (default: "LevtechCareerJob")salary_min number nullablesalary_max number nullablesalary_currency string nullableid string requiredurl string requiredis_active boolean nullableposted_at integer nullabledescription string nullablerequired_skills string nullablepreferred_skills string nullableeducation string nullableincentives string nullableemployment_types array (default: [])job_types array (default: [])@type string (default: "LevtechCareerLabel")id string nullablename string requiredcategory string nullablepositions array (default: [])skills array (default: [])@type string (default: "LevtechCareerLabel")id string nullablename string requiredcategory string nullableindustries array (default: [])@type string (default: "LevtechCareerIndustryGroup")category string nullableindustries array (default: [])work_locations array (default: [])address string nullablelatitude number nullablelongitude number nullablelocation_change_scope string nullableworking_hours string nullableworking_hours_notes string nullableflex_time string nullableflex_time_status string nullablecore_time string nullableaverage_overtime string nullableannual_holidays string nullableholidays string nullableholiday_notes string nullableremote_work_options array (default: [])side_job array (default: [])dress_code string nullableprobation_period string nullableemployment_period string nullablecontract_renewal string nullablecontract_renewal_criteria string nullablecontract_renewal_limit string nullableinsurance string nullablebenefits string nullablebenefits_notes string nullableallowances string nullabletraining string nullableevaluation_system string nullablework_phases array (default: [])interview_location string nullableaptitude_tests string nullablerequired_documents string nullablehiring_notes string nullablecompany object nullable@type string (default: "LevtechCareerJobCompany")id string requiredurl string requiredname string nullablewebsite string nullablecompany_jobs array (default: [])@type string (default: "LevtechCareerJobRef")salary_min number nullablesalary_max number nullablesalary_currency string nullableid string requiredurl string requiredis_closed boolean nullableis_new boolean nullableremote_work_policy string nullablecan_work_remotely boolean nullabledescription string nullablerequired_skills string nullableideal_candidate string nullableemployment_types array (default: [])job_types array (default: [])@type string (default: "LevtechCareerLabel")id string nullablename string requiredcategory string nullableindustries array (default: [])@type string (default: "LevtechCareerLabel")id string nullablename string requiredcategory string nullableskills array (default: [])features array (default: [])stations array (default: [])@type string (default: "LevtechCareerStation")id string nullablename string requiredline string nullableprefecture string nullablecompany object nullable@type string (default: "LevtechCareerCompanyRef")id string requiredurl string requiredname string nullable422 — 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 job 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.