/levtech/career/jobs/search

POST /api/levtech/career/jobs/search

Price: 10 credits

Search permanent engineering jobs on Levtech Career (career.levtech.jp) by keyword, skill, job type, industry, job and company features, prefecture, salary range, remote work, side jobs and no-experience openings. Each result carries the title, company name, salary range, job types, employment types, features, nearest station, job description and required skills; closed jobs are included unless open_only is set.

How to use it

A search returns at most 1,500 jobs; set open_only to skip jobs no longer taking applications. Skills of different kinds must all match, skills of one kind any of. Pass a result's id to levtech/career/jobs for the full posting and its company id.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of jobs to return (min: 1; max: 1500)
• keyword string nullable — Search words (examples: "Python", "SRE"; minLength: 1)
• skills array nullable — Skill names (examples: ["Python","AWS"]; minItems: 1)
• job_types array nullable — Job types, any of (examples: ["サーバーサイドエンジニア","SRE"]; minItems: 1)
• industries array nullable — Industries, any of (examples: ["ソフトウェア"]; minItems: 1)
• job_features array nullable — Job features, any of (examples: ["フレックス制"]; minItems: 1)
• company_features array nullable — Company features, any of (examples: ["上場企業"]; minItems: 1)
• prefectures array nullable — Prefectures, any of (one of: "hokkaido", "aomori", "iwate", "miyagi", "akita", "yamagata", "fukushima", "ibaraki", "tochigi", "gunma", "saitama", "chiba", "tokyo", "kanagawa", "niigata", "toyama", "ishikawa", "fukui", "yamanashi", "nagano", "gifu", "shizuoka", "aichi", "mie", "shiga", "kyoto", "osaka", "hyogo", "nara", "wakayama", "tottori", "shimane", "okayama", "hiroshima", "yamaguchi", "tokushima", "kagawa", "ehime", "kochi", "fukuoka", "saga", "nagasaki", "kumamoto", "oita", "miyazaki", "kagoshima", "okinawa")
• salary_min integer nullable — Minimum annual salary in JPY (examples: 6000000; min: 1)
• salary_max integer nullable — Maximum annual salary in JPY (examples: 9000000; min: 1)
• remote_only boolean — Only jobs allowing remote work (default: false)
• side_job_only boolean — Only jobs allowing side jobs (default: false)
• no_experience_ok boolean — Only jobs open to applicants without experience (default: false)
• open_only boolean — Only jobs open for applications (default: false)
• sort string — Result order (default: "recommended"; one of: "recommended", "newest", "salary")

Response

• @type string (default: "LevtechCareerJobCard")
• salary_min number nullable
• salary_max number nullable
• salary_currency string nullable
• id string required
• url string required
• company_name string nullable
• company_image string nullable
• is_closed boolean nullable
• is_new boolean nullable
• is_remote boolean nullable
• description string nullable
• required_skills string nullable
• employment_types array (default: [])
• job_type_names array (default: [])
• features array (default: [])
• station string nullable

Errors

• 422 — An unknown enum value, skill, job type, industry or feature name 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.