Playground Sign in Start free
Jobs · lever.co

How to scrape Lever

Lever is a jobs site where you can find employment listings and related information. Developers typically collect job postings, company details, and application information from its public pages.

Ujeebu scrapes any public website. Not listed here? Try any URL in the Playground or ask us about a site.

Working 1 credit a page, about $0.10 per 1,000 on Pro

21 of 21 of our checks passed in the last 7 days (100%).

Last check 2026-11-22 17:35 UTC · last pass 2026-11-22 17:35 UTC · checked with our own requests, never customer data.

Try it in the Playground

Recipe one call

Use the Lever recipe: send the URL, get JSON

1 credit a page
curl -G 'https://api.ujeebu.com/scrape' \
  -H "ApiKey: $UJEEBU_API_KEY" \
  --data-urlencode 'url=https://jobs.lever.co/matchgroup' \
  --data-urlencode 'recipe=lever/listing'

The answer is {"result": {...}} with the fields of the recipe. Billed like any /scrape call: successful responses cost credits; blocked, timed-out and failed requests are free.

Run the code on this page with your own key: 5,000 free credits for 7 days, no card. Get a free API key →

Recipes

Call a recipe by name with the recipe parameter: the Scrape API applies its extract rules and the settings that work on Lever. Each recipe was run on two real Lever pages and keeps only the fields that came back on both; it is checked again every week, and hidden if it stops working.

Search and listing pages

Validated 2026-11-14

One call: recipe=lever/listing 1 credit a page

curl -G 'https://api.ujeebu.com/scrape' \
  -H "ApiKey: $UJEEBU_API_KEY" \
  --data-urlencode 'url=https://jobs.lever.co/matchgroup' \
  --data-urlencode 'recipe=lever/listing'

The answer is {"result": {...}} with the fields below; the Ujb-Recipe header names the version (for example lever/listing@v1) and Ujb-Credits the cost.

What this recipe extracts

FieldTypeExample
jobslist of 3+ items
jobs[].companytextMatch Group
jobs[].departmenttext
jobs[].employment_typetextFull-time
jobs[].locationtextTokyo
jobs[].remotetextHybrid
jobs[].teamtextEureka
jobs[].titletextBack-end Engineer, Product (Go)
jobs[].urlURLhttps://jobs.lever.co/matchgroup/4f3e70ea-d843-4666-844a-c0ba07f2033f

Examples from jobs.lever.co/matchgroup on 2026-11-14, shortened.

Sample output (real, trimmed)

{
    "jobs": [
        {
            "company": "Match Group",
            "department": null,
            "employment_type": "Full-time",
            "location": "Tokyo",
            "remote": "Hybrid",
            "team": "Eureka",
            "title": "Back-end Engineer, Product (Go)",
            "url": "https://jobs.lever.co/matchgroup/4f3e70ea-d843-4666-844a-c0ba07f2033f"
        },
        {
            "company": "Match Group",
            "department": null,
            "employment_type": "Full-time",
            "location": "Tokyo",
            "remote": "Hybrid",
            "team": "Eureka",
            "title": "Back-end Engineer, Trust & Safety (Go)",
            "url": "https://jobs.lever.co/matchgroup/750053cb-5ace-444a-9c64-070fb4d46439"
        },
        {
            "company": "Match Group",
            "department": null,
            "employment_type": "Full-time",
            "location": "Tokyo",
            "remote": "Hybrid",
            "team": "Eureka",
            "title": "Data Product Engineer, Data Enabling",
            "url": "https://jobs.lever.co/matchgroup/849c888a-0348-4794-9c8d-5e4da7e76b2d"
        }
    ]
}
extract_rules (1 rule): the rules behind the recipe

The API applies these rules and the settings js=false for you when you send recipe=lever/listing. To change what comes back, send your own extract_rules (they replace the recipe's) or any setting (yours always win). Sites without a recipe work the same way with extract rules.

{
    "jobs": {
        "type": "fn",
        "fn": "const co = (document.title || '').trim() || null; return [...document.querySelectorAll('div.posting')].map(p => { const q = s => { const e = p.querySelector(s); return e ? e.textContent.replace(/\\s+/g, ' ').replace(/\\s*[—/]\\s*$/, '').trim() : null; }; const a = p.querySelector('a.posting-title') || p.querySelector('a.posting-btn-submit');  const g = p.closest('.postings-group'); const h = g && g.querySelector('.large-category-header, .posting-category-title'); const w = q('span.workplaceTypes');  return { url: a ? a.getAttribute('href') : null, title: q(\"h5[data-qa='posting-name']\"), company: co, team: h ? h.textContent.trim() : null, employment_type: q('span.commitment'), location: q('span.location'), remote: w, department: q('span.department') }; }).filter(x => x.url && x.title);"
    }
}

Job postings

Validated 2026-11-14

One call: recipe=lever/detail 1 credit a page

curl -G 'https://api.ujeebu.com/scrape' \
  -H "ApiKey: $UJEEBU_API_KEY" \
  --data-urlencode 'url=https://jobs.lever.co/spotify/a4c49acb-a095-4452-ad9e-69e4b778c256' \
  --data-urlencode 'recipe=lever/detail'

The answer is {"result": {...}} with the fields below; the Ujb-Recipe header names the version (for example lever/detail@v1) and Ujb-Credits the cost.

What this recipe extracts

FieldTypeExample
titletextSpotify - Senior Applied Research Scientist - Personalization
descriptiontextThe Personalization team makes deciding what to play next easier an...
remotetextRemote
departmenttextData and Analytics – Personalization /
job.companytextSpotify
job.employment_typetextPermanent
job.locationtextStockholm; London
job.posteddate2026-09-21
urlURLhttps://jobs.lever.co/spotify/a4c49acb-a095-4452-ad9e-69e4b778c256

Examples from jobs.lever.co/spotify/a4c49acb-a095-4452-ad9e-69e4b778c256 on 2026-11-14, shortened.

Sample output (real, trimmed)

{
    "job": {
        "company": "Spotify",
        "employment_type": "Permanent",
        "location": "Stockholm; London",
        "posted": "2026-09-21"
    },
    "title": "Spotify - Senior Applied Research Scientist - Personalization",
    "description": "The Personalization team makes deciding what to play next easier and more enjoyable for every listener. From Blend to Discover Weekly, we're behind some of S...",
    "remote": "Remote",
    "department": "Data and Analytics – Personalization /",
    "url": "https://jobs.lever.co/spotify/a4c49acb-a095-4452-ad9e-69e4b778c256"
}
extract_rules (6 rules): the rules behind the recipe

The API applies these rules and the settings js=false for you when you send recipe=lever/detail. To change what comes back, send your own extract_rules (they replace the recipe's) or any setting (yours always win). Sites without a recipe work the same way with extract rules.

{
    "title": {
        "selector": "meta[property=\"og:title\"]",
        "type": "attr",
        "attribute": "content"
    },
    "description": {
        "selector": "meta[property=\"og:description\"]",
        "type": "attr",
        "attribute": "content"
    },
    "remote": {
        "selector": ".posting-categories .workplaceTypes",
        "type": "text"
    },
    "department": {
        "selector": ".posting-categories .department",
        "type": "text"
    },
    "job": {
        "type": "fn",
        "fn": "const __r = (() => { const n = [...document.querySelectorAll('script[type=\"application/ld+json\"]')].flatMap(s => { try { return [].concat(JSON.parse(s.textContent)); } catch (e) { return []; } }).find(x => x && x['@type'] === 'JobPosting'); if (!n) return null; const bs = n.baseSalary && n.baseSalary.value; const c = document.querySelector('.posting-categories .commitment'); const locs = [].concat(n.jobLocation || []).map(p => p && p.address ? [p.address.addressLocality, p.address.addressRegion, p.address.addressCountry].filter(Boolean).join(', ') : null).filter(Boolean); const lc = document.querySelector('.posting-categories .location'); return { company: n.hiringOrganization ? n.hiringOrganization.name : null, location: locs.join('; ') || (lc ? lc.textContent.trim() : null), employment_type: c ? c.textContent.replace(/\\s*\\/\\s*$/, '').trim() : (n.employmentType || null), posted: n.datePosted || null, valid_through: n.validThrough || null,  salary: bs ? [bs.minValue, bs.maxValue].filter(v => v != null).join(' - ') + (bs.unitText ? ' per ' + String(bs.unitText).toLowerCase() : '') : null, salary_currency: n.baseSalary ? n.baseSalary.currency || null : null }; })(); if (!__r) return null; const __o = {}; for (const k of [\"company\",\"employment_type\",\"location\",\"posted\"]) if (__r[k] !== undefined && __r[k] !== null) __o[k] = __r[k]; return __o;"
    },
    "url": {
        "selector": "meta[property=\"og:url\"]",
        "type": "attr",
        "attribute": "content"
    }
}

Code

Complete scripts: set the UJEEBU_API_KEY environment variable and run them as they are. Each one calls the recipe by name (the Go SDK has no recipe field, so the Go script sends the recipe's rules and settings itself), prints the extracted JSON, and prints the credits the request cost (the Ujb-Credits response header) on stderr. A non-200 answer stops the script with the API's error message.

Search and listing pages

Runs the recipe on the two pages it was validated on, one after the other.

lever_listing_sdk.py pip install ujeebu-python==0.1.5
# Scrape Lever search and listing pages with the Ujeebu Scrape API.
# Calls the recipe lever/listing: the API applies its extract rules and validated settings (validated 2026-11-14). Send extract_rules or any setting to override them.
# Uses the official SDK ujeebu-python 0.1.5: pip install ujeebu-python==0.1.5
# Run: UJEEBU_API_KEY=your_key python3 lever_listing_sdk.py

import json
import os
import sys
import time

import requests
from ujeebu_python import UjeebuClient

API_KEY = os.environ.get("UJEEBU_API_KEY")
URLS = [
    "https://jobs.lever.co/matchgroup",
    "https://jobs.lever.co/palantir",
]
RECIPE = "lever/listing"  # rules and settings come from the recipe; add your own to override them


def scrape(client, url):
    # a GET with recipe=: the API applies the recipe and answers {"result": {...}}
    try:
        response = client.scrape(url, params={"recipe": RECIPE})
    except requests.RequestException as error:
        sys.exit(f"Request failed for {url}: {error}")
    if response.status_code != 200:
        try:
            message = response.json().get("message", response.text)
        except ValueError:
            message = response.text
        sys.exit(f"HTTP {response.status_code} for {url}: {str(message)[:300]}")
    print(f"Ujb-Credits: {response.headers.get('Ujb-Credits')}, Ujb-Recipe: {response.headers.get('Ujb-Recipe')}", file=sys.stderr)
    return response.json()["result"]


if not API_KEY:
    sys.exit("Set the UJEEBU_API_KEY environment variable.")

client = UjeebuClient(api_key=API_KEY)

for i, url in enumerate(URLS):
    if i:
        time.sleep(2)  # be polite: one page at a time
    result = scrape(client, url)
    for item in result.get("jobs") or []:
        print(item.get("title"), item.get("company"), item.get("location"))
    # Example output:
    # Back-end Engineer, Product (Go) Match Group Tokyo
    # Back-end Engineer, Trust & Safety (Go) Match Group Tokyo
    # every field: print(json.dumps(result, indent=2, ensure_ascii=False))

Job postings

Runs the recipe on the two pages it was validated on, one after the other.

lever_detail_sdk.py pip install ujeebu-python==0.1.5
# Scrape Lever job postings with the Ujeebu Scrape API.
# Calls the recipe lever/detail: the API applies its extract rules and validated settings (validated 2026-11-14). Send extract_rules or any setting to override them.
# Uses the official SDK ujeebu-python 0.1.5: pip install ujeebu-python==0.1.5
# Run: UJEEBU_API_KEY=your_key python3 lever_detail_sdk.py

import json
import os
import sys
import time

import requests
from ujeebu_python import UjeebuClient

API_KEY = os.environ.get("UJEEBU_API_KEY")
URLS = [
    "https://jobs.lever.co/spotify/a4c49acb-a095-4452-ad9e-69e4b778c256",
    "https://jobs.lever.co/matchgroup/4f3e70ea-d843-4666-844a-c0ba07f2033f",
]
RECIPE = "lever/detail"  # rules and settings come from the recipe; add your own to override them


def scrape(client, url):
    # a GET with recipe=: the API applies the recipe and answers {"result": {...}}
    try:
        response = client.scrape(url, params={"recipe": RECIPE})
    except requests.RequestException as error:
        sys.exit(f"Request failed for {url}: {error}")
    if response.status_code != 200:
        try:
            message = response.json().get("message", response.text)
        except ValueError:
            message = response.text
        sys.exit(f"HTTP {response.status_code} for {url}: {str(message)[:300]}")
    print(f"Ujb-Credits: {response.headers.get('Ujb-Credits')}, Ujb-Recipe: {response.headers.get('Ujb-Recipe')}", file=sys.stderr)
    return response.json()["result"]


if not API_KEY:
    sys.exit("Set the UJEEBU_API_KEY environment variable.")

client = UjeebuClient(api_key=API_KEY)

for i, url in enumerate(URLS):
    if i:
        time.sleep(2)  # be polite: one page at a time
    result = scrape(client, url)
    job = result.get("job") or {}
    print(result.get("title"), job.get("company"), job.get("location"), job.get("posted"))
    # Example output: Spotify - Senior Applied Research Sci... Spotify Stockholm; London 2026-09-21
    # every field: print(json.dumps(result, indent=2, ensure_ascii=False))

SDK tabs use the official Ujeebu SDKs (ujeebu-python 0.1.5, @ujeebu-org/ujeebu-sdk 0.1.2, github.com/ujeebu/ujeebu-go v0.1.8); there is no PHP SDK, so the PHP tab calls the API with curl. For agents and scripts, the same status and settings are at /scrape/lever.json.

Try it yourself

Run this on Lever with your own key

Get a free API key, set UJEEBU_API_KEY and run any script above as it is. 5,000 free credits for 7 days, no card.

URL patterns and pagination

What the URLs look like, read from the pages our checks fetched.

Search and listing pages

Pattern
https://jobs.lever.co/{slug}
Next pages
We did not see a next-page link on the pages we fetched. Results may load as you scroll: try scroll_down.
Validated on
https://jobs.lever.co/matchgrouphttps://jobs.lever.co/palantir

Job postings

Pattern
https://jobs.lever.co/{slug}/{id}
Validated on
https://jobs.lever.co/spotify/a4c49acb-a095-4452-ad9e-69e4b778c256https://jobs.lever.co/matchgroup/4f3e70ea-d843-4666-844a-c0ba07f2033f

Settings that work today

From our health checks over the last 7 days: the cheapest settings that return the real page most of the time.

Endpoint/scrape
jstrue
Costup to 5 credits a request

Each public page is one request: change the path in the URL to fetch another one. Collect detail page URLs from listing pages first, then fetch each detail page. Our checks run with JavaScript rendering on (js=true): keep it on.

Try it in the Playground

What people build with Lever data

  • Job market analyticsCount open roles by company, location and type to see who is hiring and where.More on this use case
  • Job aggregationCollect new postings into your own job board or alerts, with the link back to the original posting.

Limits and etiquette

  • Public pages only. Pages behind a login, and data shown only to signed-in users, are out of scope.
  • Keep the rate modest: fetch pages one after another or with low concurrency, and cache what you already have.
  • robots.txt of jobs.lever.co (read 2026-11-17): public pages allowed for generic crawlers; crawl delay 1 s.
  • Read Lever's terms of service before you collect data at scale, and do not collect personal data you have no basis to process. This guide is not legal advice.

Questions

Can you scrape Lever with Ujeebu?

Yes. 21 of 21 checks of public Lever pages passed in the last 7 days with the settings on this page.

Which settings work for Lever?

Call /scrape with js=true.

How many credits does a Lever request cost?

With these settings a request costs up to 5 credits. Only responses with HTTP 200 or 404 are billed: a blocked or timed-out request is free.

Which fields can I extract from Lever?

With the extraction recipes on this page, validated on real Lever pages through our API: search and listing pages: company, employment_type, location, remote, team, title, url; job postings: title, description, remote, department, company, employment_type, location, posted, url. Pass the recipe as extract_rules in a POST to /scrape and the API returns those fields as JSON.

Is it allowed to scrape Lever?

Its robots.txt allows generic crawlers on the page types in this guide. It asks for 1 seconds between requests. Collect public pages only, read Lever's terms of service, keep your request rate modest and do not collect personal data you have no basis to process. This is not legal advice.

How fresh is this page?

The status and settings come from our own health checks of lever.co, which run around the clock. Last check: 2026-11-22 17:35:07 UTC; last pass: 2026-11-22 17:35:07 UTC.