Greenhouse & Lever Jobs Scraper & Monitor

Scrape and monitor public company career boards on Greenhouse and Lever, then receive one normalized dataset row per real opening. The Greenhouse and Lever jobs scraper is designed for recruiters, staffing firms, sales teams, job aggregators, and hiring-signal workflows that need repeatable fresh-job data without brittle career-page HTML.

The Actor calls only the official public job-board endpoints documented by Greenhouse and Lever. It does not log in, submit applications, access candidate data, or fetch arbitrary URLs.

Why use it

• Monitor up to 20 Greenhouse and Lever boards in one bounded run.
• Normalize both providers into one stable output contract.
• Filter by job-title and location keywords before rows are emitted.
• Use onlyNew with stateStoreName to emit only openings not seen on earlier runs.
• Get honest partial-failure reporting in RUN_SUMMARY; failed boards and diagnostics are never dataset rows.
• Pay only for useful dataset rows under the Actor's pay-per-event pricing.

Quick start

{
  "boards": [
    { "provider": "greenhouse", "slug": "stripe", "companyName": "Stripe" },
    { "provider": "lever", "slug": "palantir", "companyName": "Palantir" }
  ],
  "titleKeywords": ["engineer", "developer"],
  "maxJobsPerBoard": 25,
  "onlyNew": false
}

The slug is the company-specific final path segment used by the public ATS board. For Greenhouse, stripe maps to the documented boards-api.greenhouse.io/v1/boards/stripe/jobs pattern. For Lever, palantir maps to api.lever.co/v0/postings/palantir.

For a recurring monitor, choose a stable state name and schedule the Actor with onlyNew: true:

{
  "boards": [{ "provider": "greenhouse", "slug": "stripe", "companyName": "Stripe" }],
  "onlyNew": true,
  "stateStoreName": "stripe-engineering-watch"
}

The first run treats every matching opening as new. Later runs suppress jobs already present in that named state store.

Output

Each successful row contains:

• jobId: stable provider + board + posting identifier
• provider, boardSlug, and optional user-supplied company
• title, location, team, department, commitment, and workplaceType when the source exposes them
• a bounded plain-text description
• public job and application URLs
• source timestamps when available, capturedAt, and isNew

Example:

{
  "jobId": "lever:palantir:example-id",
  "provider": "lever",
  "boardSlug": "palantir",
  "company": "Palantir",
  "title": "Software Engineer",
  "location": "New York, NY",
  "team": "Engineering",
  "department": "Product Development",
  "commitment": "Full-time",
  "workplaceType": "hybrid",
  "descriptionText": "Build reliable products...",
  "jobUrl": "https://jobs.lever.co/palantir/example-id",
  "applyUrl": "https://jobs.lever.co/palantir/example-id/apply",
  "createdAt": "2026-09-19T08:00:00.000Z",
  "updatedAt": null,
  "sourceUrl": "https://api.lever.co/v0/postings/palantir?mode=json",
  "capturedAt": "2026-09-20T10:00:00.000Z",
  "isNew": true
}

Fields not provided by an ATS remain null; the Actor does not invent them. RUN_SUMMARY is stored separately and records processed boards, failures, duplicates, and only-new suppression.

Pricing and limits

The Store price is $0.003 per delivered job row. Invalid inputs, failed boards, duplicates, suppressed old jobs, and the run summary are not billed as results.

• 1–20 boards per run
• 1–500 accepted jobs per board
• up to 10 title filters and 10 location filters
• four total attempts at most for transient 408, 429, or 5xx responses
• 45-second maximum per request and a 10 MB response limit
• state is capped to prevent unbounded storage growth

Limitations

• Only public, published jobs exposed by the two documented ATS endpoints are included.
• This is a board monitor, not a cross-company search engine; customers supply the company board slugs they want to watch.
• Greenhouse does not expose a reliable created timestamp in its public list response, so createdAt is null; updatedAt is preserved when supplied.
• Lever EU boards require leverRegion: "eu".
• A valid but empty public board succeeds with zero result rows. A missing, private, or malformed board is reported as a failure; the run fails if every requested board fails.

API example

curl -X POST "https://api.apify.com/v2/acts/technicaldost~greenhouse-lever-fresh-jobs-monitor/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"boards":[{"provider":"greenhouse","slug":"stripe","companyName":"Stripe"}],"maxJobsPerBoard":10}'

Keep Apify tokens in environment variables or a secrets manager; do not commit them or place them in URLs or shared logs.

Local verification

npm ci
npm test

Source behavior is covered with fixtures/mocks for validation, normalization, filtering, only-new state, retries, partial failure, and schema integrity. Release smoke tests use real public Greenhouse and Lever boards with a one-row cap.

Input example

{
  "boards": [
    {
      "provider": "greenhouse",
      "slug": "stripe"
    },
    {
      "provider": "lever",
      "slug": "palantir"
    }
  ]
}

All fields are described in the Input tab, and the same JSON works in the API and for AI agents.

Use Greenhouse & Lever Jobs Scraper & Monitor with AI agents (MCP)

Give Claude, ChatGPT, Cursor, VS Code or any MCP client this Actor as a tool through the hosted Apify MCP server. The agent sees the input fields with descriptions and example values, runs the Actor, and reads the results.

MCP server URL (this Actor only):

https://mcp.apify.com/?tools=technicaldost/greenhouse-lever-fresh-jobs-monitor

Claude Code:

$claude mcp add --transport http apify "https://mcp.apify.com/?tools=technicaldost/greenhouse-lever-fresh-jobs-monitor" --header "Authorization: Bearer YOUR_APIFY_TOKEN"

Cursor, VS Code, Claude Desktop and other clients (mcp.json or the client's MCP settings):

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?tools=technicaldost/greenhouse-lever-fresh-jobs-monitor",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}

Clients that support sign-in (such as Claude.ai connectors) can use the URL without a token and log in to Apify instead. Get your token in Apify Console → Settings → API & Integrations, or generate a ready config for your client at mcp.apify.com. In the agent the tool is named technicaldost--greenhouse-lever-fresh-jobs-monitor; ask it, for example, to "run Greenhouse & Lever Jobs Scraper & Monitor with {"boards": [{"provider": "greenhouse", "slug": "stripe"}, {"provider": "lever", "slug": "palantir"}]}".

AI agents without an Apify account can also run and pay for this Actor per request with x402 agentic payments.

Run Greenhouse & Lever Jobs Scraper & Monitor via API

Run the Actor and get its results in one call (replace YOUR_APIFY_TOKEN):

curl -X POST "https://api.apify.com/v2/acts/technicaldost~greenhouse-lever-fresh-jobs-monitor/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"boards": [{"provider": "greenhouse", "slug": "stripe"}, {"provider": "lever", "slug": "palantir"}]}'

Python (pip install apify-client):

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("technicaldost/greenhouse-lever-fresh-jobs-monitor").call(run_input={"boards": [{"provider": "greenhouse", "slug": "stripe"}, {"provider": "lever", "slug": "palantir"}]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript / TypeScript (npm install apify-client):

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('technicaldost/greenhouse-lever-fresh-jobs-monitor').call({"boards": [{"provider": "greenhouse", "slug": "stripe"}, {"provider": "lever", "slug": "palantir"}]});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Long runs: start them with POST /v2/acts/technicaldost~greenhouse-lever-fresh-jobs-monitor/runs and fetch the dataset when the run finishes, or receive a webhook.

Integrations

Greenhouse & Lever Jobs Scraper & Monitor works with Make, Zapier, n8n, LangChain, Google Sheets, Slack, GitHub and webhooks. Schedule runs in Apify Console and send new results straight to your apps, spreadsheets or AI pipelines.

Related Actors

• Google Jobs Scraper & Fresh Lead Monitor — Scrape public Google Jobs results by query and location into structured job leads with employer, source, posti
• Greenhouse Lever Ashby Jobs API — Scrape job postings from 5 public ATS APIs: Greenhouse, Lever, Ashby, Workable and SmartRecruiters. Returns ti
• Cutshort Jobs Scraper - Tech Jobs India — Scrape Cutshort tech job listings by skill and city: company profile, salary range, experience range, skills
• iimjobs Jobs Scraper - Management & MBA Jobs India — Scrape iimjobs management and MBA job listings by keyword and city: company, experience range, salary in lakhs

FAQ

Can I use Greenhouse & Lever Jobs Scraper & Monitor with AI agents like Claude or ChatGPT?

Yes. Connect the Apify MCP server with ?tools=technicaldost/greenhouse-lever-fresh-jobs-monitor (see above) and the agent can run the Actor and read its results on its own.

Can I call Greenhouse & Lever Jobs Scraper & Monitor from my own code?

Yes. Use the REST API, or the official Python and JavaScript clients shown above. Results are available as JSON, CSV, Excel, XML or HTML.

How do I run it on a schedule?

Save your input as a task in Apify Console and add a schedule (for example, daily). Use webhooks or integrations to send each run's results onward.

Is it legal to use this Actor?

It works with publicly available data. Make sure your use complies with the source website's terms and with data protection laws such as GDPR, especially for personal data.

Something doesn't work or I need a feature. What should I do?

Open an issue in the Issues tab on this Actor's page with an example input, and we'll look into it.