Greenhouse & Lever Fresh Jobs Monitor

Monitor public company career boards on Greenhouse and Lever and receive one normalized dataset row per real opening. It is designed for recruiters, staffing firms, sales teams, job aggregators, and hiring-signal workflows that need repeatable fresh-job data without scraping 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 planned 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?token=YOUR_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 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.