/lever/jobs/search

POST /api/lever/jobs/search

Price: 10 credits

List job postings from a company's Lever career board by board handle, optionally narrowed by team, location, commitment type or department. Each posting includes title, team, department, location, commitment, workplace type, country, descriptions, structured sections, creation date and apply URL.

How to use it

List the job postings of a specific company's Lever career board. company is the board handle (e.g. spotify); count is how many postings to return. Optional team, location, commitment and department filters narrow the results. Each item has id, title, team, department, location, all_locations, commitment, workplace_type, country, description and description_plain, sections, additional info, created_at, hosted_url and apply_url.

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 job-board handle from the careers URL (jobs.lever.co/{company}) (examples: "spotify", "shieldai", "gopuff"; minLength: 1)
• count integer required — Max number of job postings to return (min: 1)
• team string nullable — Filter by team (examples: "Accounting", "Engineering")
• location string nullable — Filter by location (examples: "London", "New York, NY")
• commitment string nullable — Filter by commitment type (examples: "Permanent", "Full Time", "Intern")
• department string nullable — Filter by department (examples: "Finance", "Engineering")

Response

• @type string (default: "LeverJob")
• id string required
• team string nullable
• department string nullable
• location string nullable
• all_locations array (default: [])
• commitment string nullable
• workplace_type string nullable
• country string nullable
• opening string nullable
• opening_plain string nullable
• description string nullable
• description_plain string nullable
• description_body string nullable
• description_body_plain string nullable
• sections array (default: [])
  • @type string (default: "LeverJobSection")
  • text string nullable
  • content string nullable
• additional string nullable
• additional_plain string nullable
• salary_range object nullable
  • @type string (default: "LeverSalaryRange")
  • currency string nullable
  • interval string nullable
  • min number nullable
  • max number nullable
• salary_description string nullable
• salary_description_plain string nullable
• created_at integer nullable
• hosted_url string nullable
• apply_url 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 — Company board not found 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.