POST /api/levtech/career/companies
Price: 20 credits
Get one company on Levtech Career (career.levtech.jp): business description, culture, founding date, representative, capital, headcount, website, insurance, benefits, holidays, tech stack by category, feature articles, photos, its job count and job types, and similar companies.
Find company ids in company.id of levtech/career/jobs; levtech/career/companies/jobs lists the company's jobs.
access-token string requiredtimeout 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)@type string (default: "LevtechCareerCompany")id string requiredurl string requiredname string nullableimage string nullablephotos array (default: [])description string nullableculture string nullablefounded_at integer nullablerepresentative string nullablecapital number nullablecapital_currency string nullableemployee_count integer nullablewebsite string nullableinsurance string nullablebenefits string nullableholidays string nullableholiday_notes string nullableallowances string nullablejob_count integer nullablejob_types array (default: [])@type string (default: "LevtechCareerLabel")id string nullablename string requiredcategory string nullabletech_stack array (default: [])@type string (default: "LevtechCareerTechGroup")category string requiredskills array (default: [])articles array (default: [])@type string (default: "LevtechCareerArticle")text string nullablesimilar_companies array (default: [])@type string (default: "LevtechCareerSimilarCompany")id string requiredurl string requiredname string nullabledescription string nullablecapital number nullableindustry string nullableupdated_at integer 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 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.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.